public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113915] New: [14 regression] glibc miscompiled for armv7a since r14-4365-g0731889c026bfe Date: Wed, 14 Feb 2024 02:41:08 +0000 [thread overview] Message-ID: <bug-113915-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113915 Bug ID: 113915 Summary: [14 regression] glibc miscompiled for armv7a since r14-4365-g0731889c026bfe Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: sjames at gcc dot gnu.org CC: ramana at gcc dot gnu.org, wilco at gcc dot gnu.org Target Milestone: --- glibc seems to go from 30 failing innocent tests (*) to over 400 between gcc-13 and gcc-14. Bisected to r14-4365-g0731889c026bfe which fixed PR111235. It's hard to know where to start with this. I'll try the usual bisection of objects and then pragmas although I fear the (necessary) complexities of glibc's build system may make my usual method tricky. We'll see... I've bisected using glibc's posix/tst-getopt-cancel test as it had easy output to grep for: ``` $ cat ./posix/tst-getopt-cancel.out begin: no errors Didn't expect signal from child: got `Segmentation fault' ``` (*) just from sandboxing stuff, they're normally not there and should be unrelated given they happened w/ 13.
next reply other threads:[~2024-02-14 2:41 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-14 2:41 sjames at gcc dot gnu.org [this message] 2024-02-14 2:42 ` [Bug target/113915] " sjames at gcc dot gnu.org 2024-02-14 2:48 ` sjames at gcc dot gnu.org 2024-02-14 2:53 ` sjames at gcc dot gnu.org 2024-02-14 3:10 ` sjames at gcc dot gnu.org 2024-02-14 3:14 ` sjames at gcc dot gnu.org 2024-02-14 6:59 ` pinskia at gcc dot gnu.org 2024-02-14 6:59 ` pinskia at gcc dot gnu.org 2024-02-14 7:05 ` [Bug target/113915] [14 regression] glibc's _dl_find_object_update_1 " pinskia at gcc dot gnu.org 2024-02-14 7:16 ` pinskia at gcc dot gnu.org 2024-02-14 7:21 ` pinskia at gcc dot gnu.org 2024-02-14 7:26 ` pinskia at gcc dot gnu.org 2024-02-14 7:38 ` pinskia at gcc dot gnu.org 2024-02-14 10:07 ` rguenth at gcc dot gnu.org 2024-02-14 11:01 ` wilco at gcc dot gnu.org 2024-02-18 9:32 ` sjames at gcc dot gnu.org 2024-02-21 14:38 ` wilco at gcc dot gnu.org 2024-03-06 17:42 ` cvs-commit at gcc dot gnu.org 2024-03-06 18:00 ` wilco at gcc dot gnu.org 2024-03-08 15:05 ` cvs-commit 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-113915-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).