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 r10-10799] Darwin, testsuite : Prune 'object file not found for object'. Date: Sun, 29 May 2022 19:13:56 +0000 (GMT) [thread overview] Message-ID: <20220529191356.56A9F3829BEC@sourceware.org> (raw) https://gcc.gnu.org/g:dac09c729042c9d0b406396dd6cbc370a8526380 commit r10-10799-gdac09c729042c9d0b406396dd6cbc370a8526380 Author: Iain Sandoe <iain@sandoe.co.uk> Date: Sun Jan 10 09:48:13 2021 +0000 Darwin, testsuite : Prune 'object file not found for object'. This is not a GCC problem, but a fault in the static linker where, when a source file is used multiple times, with conditional compilation the source file is only referenced by the linker for the first object. Then, when dsymutil tries to find the source file for next object based off that source there is no record for it. gcc/testsuite/ChangeLog: * lib/prune.exp: Prune useless output caused by a linker bug. (cherry picked from commit 0d737ed2171165ba39ab5647f8a94c588fc9a898) Diff: --- gcc/testsuite/lib/prune.exp | 3 +++ 1 file changed, 3 insertions(+) diff --git a/gcc/testsuite/lib/prune.exp b/gcc/testsuite/lib/prune.exp index 83d394a5886..a5d09c78106 100644 --- a/gcc/testsuite/lib/prune.exp +++ b/gcc/testsuite/lib/prune.exp @@ -79,6 +79,9 @@ proc prune_gcc_output { text } { # Ignore harmless warnings from Xcode 4.0. 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 + # If dg-enable-nn-line-numbers was provided, then obscure source-margin # line numbers by converting them to "NN" form. set text [maybe-handle-nn-line-numbers $text]
reply other threads:[~2022-05-29 19: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=20220529191356.56A9F3829BEC@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).