public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/112728] gcc.dg/scantest-lto.c FAILs Date: Sat, 11 May 2024 16:23:44 +0000 [thread overview] Message-ID: <bug-112728-4-MC7i3J23Ma@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112728-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112728 Iain Sandoe <iains at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2024-05-11 CC| |iains at gcc dot gnu.org Status|UNCONFIRMED |NEW --- Comment #6 from Iain Sandoe <iains at gcc dot gnu.org> --- it also fails on Darwin because the LTO section names are different (and therefore are not being excluded) -- I have patches to fix the two issues mentioned for Darwin, For the EH case, we can imply omit the EH frames from the test. For the other case, I'll fix up the scanasm code to allow the correct LTO section name introducer on Darwin - that seems a better solution than doing a dance with counting the number of .ascii every time. No idea if either of those issues is relevant to the remaining affected platforms.
next prev parent reply other threads:[~2024-05-11 16:23 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-27 14:00 [Bug testsuite/112728] New: " ro at gcc dot gnu.org 2023-11-27 14:01 ` [Bug testsuite/112728] " ro at gcc dot gnu.org 2023-11-28 13:24 ` ro at gcc dot gnu.org 2023-11-29 9:30 ` cvs-commit at gcc dot gnu.org 2023-11-30 12:26 ` amylaar at gcc dot gnu.org 2023-12-01 12:56 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-05-07 7:42 ` rguenth at gcc dot gnu.org 2024-05-11 16:23 ` iains at gcc dot gnu.org [this message] 2024-05-12 12:36 ` iains at gcc dot gnu.org 2024-05-12 12:41 ` iains 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-112728-4-MC7i3J23Ma@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).