Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MNOTE messages not showing up in the assembly listing #544

Open
abekornelis opened this issue Aug 5, 2024 · 0 comments
Open

MNOTE messages not showing up in the assembly listing #544

abekornelis opened this issue Aug 5, 2024 · 0 comments
Labels
component-core Related to core components (java) Investigate Needs additional investigation Lang:Java

Comments

@abekornelis
Copy link
Collaborator

abekornelis commented Aug 5, 2024

In the assembly listing (the .PRN file) MNOTE messages do not appear as they do on HLASM assembler listings.
The MAXWARN option of z390 determines which MNOTEs are regarded as error messages, and which are only warnings.
Any MNOTE with an error level greater than the MAXWARN value is treated as an error and displayed on the listing. This is okay.
But:

  • Q1: Should messages below the treshold of MAXWARN be suppressed?
    • I think in allow mode this is okay, but in noallow mode this is incorrect: HLASM will print any MNOTE
    • in noallow mode it is still desirable to use MAXWARN to determine whether or not to count the MNOTE as an error for MAXERROR checking
  • Q2: MAXWARN(0) suppresses MNOTEs with a level 0 severity. This means there is no way to request these MNOTEs to be reported on the listing. Do we desire an option value to enable printing these MNOTEs on the listing?
  • Q3: MNOTEs with an error level of * are reported by HLASM as a generated comment line on the HLASM listing. Should z390 do likewise?
    • in allow mode, suppressing these MNOTEs might be okay
    • in noallow mode, compatability dicatates that z390 should also report these messages as generated comment lines on the .PRN file

z390 also uses MAXWARN level to decide whether ot not to route the generated message to the log file.
I think there is no need to change that, although - under current conditions - this output stream also can never be made to show any MNOTE with severity 0.

@abekornelis abekornelis added component-core Related to core components (java) Lang:Java Investigate Needs additional investigation labels Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component-core Related to core components (java) Investigate Needs additional investigation Lang:Java
Projects
None yet
Development

No branches or pull requests

1 participant