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-11344] libphobos, testsuite: Add prune clauses for two Darwin cases. Date: Tue, 23 Apr 2024 14:13:12 +0000 (GMT) [thread overview] Message-ID: <20240423141312.B29143858C50@sourceware.org> (raw) https://gcc.gnu.org/g:4a0e4f68a39c19c27456c9925c9dc85a3617ebad commit r11-11344-g4a0e4f68a39c19c27456c9925c9dc85a3617ebad Author: Iain Sandoe <iain@sandoe.co.uk> Date: Fri Nov 19 15:48:53 2021 +0000 libphobos, testsuite: Add prune clauses for two Darwin cases. Depending on the permutation of CPU, OS version and shared/non- shared library inclusion, we get can get two warnings from the external tools (ld64, dsymutil) which are not actually GCC issues but relate to the external tools. These are alrrady pruned in the main testsuite, this adds them to the library. Signed-off-by: Iain Sandoe <iain@sandoe.co.uk> libphobos/ChangeLog: * testsuite/lib/libphobos.exp: Prune warnings from external tool bugs. (cherry picked from commit 532fae74c3b1197023a765272892e12e123f0a56) Diff: --- libphobos/testsuite/lib/libphobos.exp | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/libphobos/testsuite/lib/libphobos.exp b/libphobos/testsuite/lib/libphobos.exp index 3be2092b12e..2af430a0e45 100644 --- a/libphobos/testsuite/lib/libphobos.exp +++ b/libphobos/testsuite/lib/libphobos.exp @@ -90,6 +90,13 @@ proc libphobos-dg-test { prog do_what extra_tool_flags } { } proc libphobos-dg-prune { system text } { + + # Ignore harmless warnings from Xcode. + regsub -all "(^|\n)\[^\n\]*ld: warning: could not create compact unwind for\[^\n\]*" $text "" text + + # Ignore dsymutil warning (tool bug is actually linker) + regsub -all "(^|\n)\[^\n\]*could not find object file symbol for symbol\[^\n\]*" $text "" text + return $text }
reply other threads:[~2024-04-23 14:13 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=20240423141312.B29143858C50@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).