public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/112728] gcc.dg/scantest-lto.c FAILs Date: Fri, 01 Dec 2023 12:56:44 +0000 [thread overview] Message-ID: <bug-112728-4-1uR7iOPkDl@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 --- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #3 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> --- > (In reply to Rainer Orth from comment #0) >> The gcc.dg/scantest-lto.c FAILs on quite a number of targets: > ... >> * On Darwin, the __TEXT,__eh_frame contains .ascii because the assembler >> lacks support for cfi directives. > > I suppose we could handle the darwin case by: > > - Not doing the common scan-assembler* tests for darwin I guess it would be better to use the recently introduce cfi effective-target keyword to catch targets that would show ascii in there. > - doing a scan-assembler-times test that expects exactly how many .ascii are > emitted for cfi. While that's an option, I suspect that's going too far actually.
next prev parent reply other threads:[~2023-12-01 12:56 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 [this message] 2024-05-07 7:42 ` rguenth at gcc dot gnu.org 2024-05-11 16:23 ` iains at gcc dot gnu.org 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-1uR7iOPkDl@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).