https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119377
--- Comment #22 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to James K. Lowden from comment #21) > Commit 069bf2fe31e99f0415ddb6acaf76cfb6eee8bb6a on June 9 included a change > to the lexer that corrected an uninitialized value for the SECTION token. > That error could have manifested on Darwin and lay hidden otherwise. If I see a commit from either of you - then I usually do a build with COBOL enabled to see if the situation has improved .. unfortunately that commit has not solved the underlying issue: https://gcc.gnu.org/pipermail/gcc-testresults/2025-July/853268.html the fails are still of the form (in some cases there is garbage between the '', but mostly its empty): /src-local/gcc-master/gcc/testsuite/cobol.dg/group1/declarative_1.cob:51:22: sorry, unimplemented: SECTION segment '' is not ISO syntax compiler exited with status 1 FAIL: cobol.dg/group1/declarative_1.cob -O0 (test for excess errors) Excess errors: /src-local/gcc-master/gcc/testsuite/cobol.dg/group1/declarative_1.cob:51:22: sorry, unimplemented: SECTION segment '' is not ISO syntax === different OSs can be more or less forgiving of memory management issues; I see Linux as pretty forgiving, Darwin less so and Solaris as pretty unforgiving ..
