https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113109
Bug ID: 113109 Summary: [14 Regression] g++ EH tests fail at execution time for cris-elf after r14-6674-g4759383245ac97 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: hp at gcc dot gnu.org CC: guojiufu at gcc dot gnu.org Target Milestone: --- Host: x86_64-pc-linux-gnu Target: cris-elf After r14-6674-g4759383245ac97, (at least) all tests that "throw", fail for cris-elf at execution time: g++ tests as well as libstdc++ tests. I don't see any other clues from g++.log than execution failing for those tests. Complete before/after example reports at https://gcc.gnu.org/pipermail/gcc-testresults/2023-December/803815.html and https://gcc.gnu.org/pipermail/gcc-testresults/2023-December/803816.html (for r14-6672-g605d21f8ef1f and r14-6750-gf9be3d8faa47; same failures as 6674). An example of a small hopefully-minimal test that fail is gcc/testsuite/g++.old-deja/g++.mike/eh6.C. Like for seemingly all others, execution the test fails, and there's no output from the printf. That printf-statement is likely not reached, but the output *could* possibly still be in an output-buffer (I don't remember how that works in newlib; that could happen for glibc when execution is aborted). I'm initially setting component to "middle-end" because that's what the commit touched and also, I'm biased, but visiting the gcc-testresults archives I don't see other targets fail in the same manner, so it could still be that "target" fits better. Further analysis will show; I'll dig a little deeper. (Commit author CC:ed.)