https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119377
--- Comment #14 from Sam James <sjames at gcc dot gnu.org> --- (In reply to Robert Dubner from comment #13) > But if other testcases are failing, that becomes less attractive. Let me > know. > All in all, I see: cobol.dg/group1/declarative_1.cob cobol.dg/group2/88_level_with_FALSE_IS_clause.cob cobol.dg/group2/ALLOCATE___FREE_with_BASED_item__1_.cob cobol.dg/group2/EXIT_SECTION.cob cobol.dg/group2/FLOAT-LONG_with_SIZE_ERROR.cob cobol.dg/group2/FLOAT-SHORT_with_SIZE_ERROR.cob cobol.dg/group2/FUNCTION_DATE___TIME_OMNIBUS.cob cobol.dg/group2/INSPECT_ISO_Example_1.cob cobol.dg/group2/INSPECT_ISO_Example_2.cob cobol.dg/group2/INSPECT_ISO_Example_3.cob cobol.dg/group2/INSPECT_ISO_Example_4.cob cobol.dg/group2/INSPECT_ISO_Example_5-f.cob cobol.dg/group2/INSPECT_ISO_Example_5-r.cob cobol.dg/group2/INSPECT_ISO_Example_6.cob cobol.dg/group2/INSPECT_ISO_Example_7.cob cobol.dg/group2/PERFORM_type_OSVS.cob failing. > Given how it's failing, it'll probably fail again. I say that because of > where the problem is manifesting, which is pretty high up in the parser. So, > if you can give me some guidance on setting up a Darwin development > environment, that'll be useful, so we're not trying to debug by remote > control. > Iain's on macOS, I'm just on x86-64 Linux here. > I mean, I don't have a clue even as to what compiler you are using to > compile GCC-16! It shouldn't matter with a bootstrap build, but the answer is in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119377#c0 (trunk building trunk, but I see the same with 15).
