public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Iain D Sandoe <iains@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r11-11379] testsuite, Darwin: Skip g++.dg/debug/dwarf2/pr85550.C Date: Sat, 27 Apr 2024 16:10:28 +0000 (GMT) [thread overview] Message-ID: <20240427161028.88F023858D1E@sourceware.org> (raw) https://gcc.gnu.org/g:b7c784f58fa7b4afe4cd8546a698df03b88b6fed commit r11-11379-gb7c784f58fa7b4afe4cd8546a698df03b88b6fed Author: Iain Sandoe <iain@sandoe.co.uk> Date: Sun Oct 1 20:38:44 2023 +0100 testsuite, Darwin: Skip g++.dg/debug/dwarf2/pr85550.C There are two problems here; first that the emitted asm for -fdebug-types-section is ELF-specfic leading to assembler errors for Mach-O. If we fix this, we get a secondary fail since the debug linker does not recognise DW_FORM_ref_sig8. Disable ths test until we get DWARF-5 support in the external Darwin toolchain components. gcc/testsuite/ChangeLog: * g++.dg/debug/dwarf2/pr85550.C: Skip for Darwin. Signed-off-by: Iain Sandoe <iain@sandoe.co.uk> (cherry picked from commit 76547f4c97b1c0744487d624c5e2e5a15d0370a9) Diff: --- gcc/testsuite/g++.dg/debug/dwarf2/pr85550.C | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/testsuite/g++.dg/debug/dwarf2/pr85550.C b/gcc/testsuite/g++.dg/debug/dwarf2/pr85550.C index 35b0f56e959..c95f75255d4 100644 --- a/gcc/testsuite/g++.dg/debug/dwarf2/pr85550.C +++ b/gcc/testsuite/g++.dg/debug/dwarf2/pr85550.C @@ -2,6 +2,7 @@ // { dg-do link } // { dg-options "-O2 -g -fdebug-types-section" } // { dg-skip-if "AIX DWARF5" { powerpc-ibm-aix* } } +// { dg-skip-if "No debug linker support" { *-*-darwin* } } struct A { int bar () const { return 0; }
reply other threads:[~2024-04-27 16:10 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240427161028.88F023858D1E@sourceware.org \ --to=iains@gcc.gnu.org \ --cc=gcc-cvs@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).