[Bug cobol/119331] cobol: unimplemented exceptions abort compilation - even if requested to NOT use them
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119331 --- Comment #5 from James K. Lowden --- Yes. One way to look at is to pretend there is no command-line option regarding ECs. The CDF behaves as required; it is up to the COBOL text to use it. :-) Under consideration: A CDF-directive command-line option, whereby any one-line CDF directive can be added, as though it existed in a file with -include. Scoop CDF directives from the command line into a "file" that is processed before all others. If we do it that way, the command-line "syntax" is COBOL, and self-documenting. Regardless, to answer your question, as a matter of priority, this issue due for treatment this year, but not in the next 60 days.
[Bug cobol/119331] cobol: unimplemented exceptions abort compilation - even if requested to NOT use them
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119331 --- Comment #4 from Simon Sobisch --- I see, so I guess you'll leave enabling in the command line interface for now and autogen+include a temporary CDF for disabling in cobcd?
[Bug cobol/119331] cobol: unimplemented exceptions abort compilation - even if requested to NOT use them
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119331 --- Comment #3 from James K. Lowden --- This patch awaits work on the command-line interface for warnings and options. As of now, ECs can be turns on and off via CDF, but can be enabled only via the command-line. That puts the compiler in compliance with ISO but out of compliance with GCC convention. As a workaround, ECs can be turned on and off as COBOL CDF text in a prepended file with the -include option. If the program (or command line) attempts to enable an unimplemented EC, the compiler really has no choice but to issue an error. The user can decide if the program is correct with the EC disabled, and make the necessary adjustment. The compiler is not so privileged. :-)
[Bug cobol/119331] cobol: unimplemented exceptions abort compilation - even if requested to NOT use them
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119331 --- Comment #2 from Simon Sobisch --- This issue keep up popping in each test run :-/ Current output of gcobc --debug -fno-ec=DATA-INCOMPATIBLE -fno-ec=PROGRAM-ARG-MISMATCH -fno-ec=PROGRAM-ARG-OMITTED warning: --debug implies -fstack-check: ignored cobol1: sorry, unimplemented: exception 'EC-DATA-INCOMPATIBLE' cobol1: sorry, unimplemented: CDF: exception 'EC-DATA-INCOMPATIBLE' cobol1: sorry, unimplemented: exception 'EC-PROGRAM-ARG-MISMATCH' cobol1: sorry, unimplemented: CDF: exception 'EC-PROGRAM-ARG-MISMATCH' cobol1: sorry, unimplemented: exception 'EC-PROGRAM-ARG-OMITTED' cobol1: sorry, unimplemented: CDF: exception 'EC-PROGRAM-ARG-OMITTED' * duplicate messages * in case of _disabling_ this should never be an error, because if the user wants to disable something you don't know and therefore not activated in the first place, then there is no reason to abort the compilation (compare with -Wno-banana - that you commonly don't even see warned on) * this should be a warning in the first place, not an error (ISO keeps adding more exceptions and there are also non-standard ones, and you likely don't handle "everything" over the next months in any case)
[Bug cobol/119331] cobol: unimplemented exceptions abort compilation - even if requested to NOT use them
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119331 James K. Lowden changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed||2025-05-18 Ever confirmed|0 |1 Assignee|unassigned at gcc dot gnu.org |jklowden at gcc dot gnu.org
[Bug cobol/119331] cobol: unimplemented exceptions abort compilation - even if requested to NOT use them
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119331 --- Comment #1 from Simon Sobisch --- Side note: there's a working patch for gcobc at https://gcc.gnu.org/pipermail/gcc-patches/2025-April/680218.html which improves it in general - but this part was explicit left out
