public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/113109] New: [14 Regression] g++ EH tests fail at execution time for cris-elf after r14-6674-g4759383245ac97 Date: Fri, 22 Dec 2023 02:12:58 +0000 [thread overview] Message-ID: <bug-113109-4@http.gcc.gnu.org/bugzilla/> (raw) 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.)
next reply other threads:[~2023-12-22 2:12 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-22 2:12 hp at gcc dot gnu.org [this message] 2023-12-22 2:22 ` [Bug middle-end/113109] " pinskia at gcc dot gnu.org 2023-12-22 2:24 ` pinskia at gcc dot gnu.org 2023-12-22 2:51 ` hp at gcc dot gnu.org 2023-12-23 2:42 ` hp at gcc dot gnu.org 2023-12-23 6:20 ` pinskia at gcc dot gnu.org 2023-12-23 17:19 ` hp at gcc dot gnu.org 2023-12-23 17:25 ` pinskia at gcc dot gnu.org 2023-12-24 0:19 ` guojiufu at gcc dot gnu.org 2023-12-24 0:34 ` guojiufu at gcc dot gnu.org 2023-12-24 0:41 ` cvs-commit at gcc dot gnu.org 2023-12-24 0:58 ` hp at gcc dot gnu.org 2023-12-24 1:01 ` hp at gcc dot gnu.org 2023-12-24 1:01 ` hp at gcc dot gnu.org 2023-12-24 1:16 ` guojiufu at gcc dot gnu.org 2023-12-24 9:13 ` hp at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-113109-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).