Apparently this is only an issue when PROC is used without any parameters for simple delineation (DEBUG.ASM does this), overall JWasm is doing what is expected by not listing the generated code unless -Sg is in effect. While MASM does handle the case of RET in a procedure without parameters or an epilogue macro in effect by always listing the sole C3h opcode this seems to be more of a minor enhancement than a bug so you can add this to the existing listing feature request ticket and close this bug.
Also another "fix" is to use option epilogue:none
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
IIRC there was already a topic about this issue.
Best "fix" is to use -Sg to show what code RET actually generated.
Speaking more generally, I'd say that the current listing status has room for improvements, but for v2.10 there are no plans to work on this area.
Apparently this is only an issue when PROC is used without any parameters for simple delineation (DEBUG.ASM does this), overall JWasm is doing what is expected by not listing the generated code unless -Sg is in effect. While MASM does handle the case of RET in a procedure without parameters or an epilogue macro in effect by always listing the sole C3h opcode this seems to be more of a minor enhancement than a bug so you can add this to the existing listing feature request ticket and close this bug.
Also another "fix" is to use option epilogue:none
Merge with Feature Requests ticket #45 "Listing requests"
Last edit: dosfan01 2013-05-13