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 debug/115066] [debug, gsplit-dwarf, gdwarf-4, g3] DW_MACRO_define_strp used for debug_str_offsets index Date: Thu, 16 May 2024 09:22:26 +0000 [thread overview] Message-ID: <bug-115066-4-jx2gg3u3qQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115066-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115066 --- Comment #12 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #11 from Tom de Vries <vries at gcc dot gnu.org> --- > (In reply to Rainer Orth from comment #10) [...] >> I wonder how best to handle this: just skip the test on sparc*-sun-solaris2* >> && !gas? Theoretically, there could be other targets with similar issues. > > This looks like test-case issue, so re-closing the PR. True, but it's often way simpler to discuss testcase issues in the original PR rather than open new PRs for every single issue with a testcase (and there's already been the comment character one here). > How about: > ... > -/* { dg-final { scan-assembler {\.byte\t0xb\t[^\n\r]* Define macro strx} } } > */ > +/* { dg-final { scan-assembler {\.byte\t0xb\t[^\n\r]* Define macro > strx|\.byte\t0x1\t[^\n\r]* Define macro} > ... > ? Seems like an option, too (and would work on other affected targets should they appear). Tested on sparc-sun-solaris2.11 with as and gas. Btw., I wonder which of the targets currently skipped with "split DWARF unsupported" are instances of this problem, too: Solaris doesn't support -gsplit-dwarf, still the test PASSes on Solaris/SPARC with gas and Solaris/x86 with either assembler.
next prev parent reply other threads:[~2024-05-16 9:22 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-13 8:40 [Bug debug/115066] New: " vries at gcc dot gnu.org 2024-05-13 8:42 ` [Bug debug/115066] " vries at gcc dot gnu.org 2024-05-13 9:12 ` vries at gcc dot gnu.org 2024-05-13 10:27 ` rguenth at gcc dot gnu.org 2024-05-13 10:29 ` vries at gcc dot gnu.org 2024-05-13 10:33 ` jakub at gcc dot gnu.org 2024-05-13 11:11 ` vries at gcc dot gnu.org 2024-05-14 11:35 ` vries at gcc dot gnu.org 2024-05-14 12:00 ` cvs-commit at gcc dot gnu.org 2024-05-14 12:04 ` vries at gcc dot gnu.org 2024-05-16 8:35 ` ro at gcc dot gnu.org 2024-05-16 9:06 ` vries at gcc dot gnu.org 2024-05-16 9:22 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2024-05-22 8:06 ` cvs-commit at gcc dot gnu.org 2024-05-27 14:02 ` clyon 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-115066-4-jx2gg3u3qQ@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).