public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114233] Newly-introduced pr113617.C test fails on Darwin Date: Thu, 07 Mar 2024 14:25:02 +0000 [thread overview] Message-ID: <bug-114233-4-MXq7xAuP5d@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114233-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114233 --- Comment #3 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> --- Jakub has posted a patch in the linker PR (thanks!). But there remains a darwin bug. The test in check_effective_target_shared actually works with C, but not with C++, because: Undefined symbols for architecture arm64: "__Z3foov", referenced from: __Z3bazv in ccCj5plO.o Why have we not seen it before? Because most of the use of that check is in { dg-require-effective-target shared } so we're effectively skipping tests, and that is silent. As far as I can tell, this addition is the first time { target shared } is used as a conditional in something like { dg-additional-options } in the C++ testsuite. The fix is simple: diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp index ae33c4f1e3a..467b539b20d 100644 --- a/gcc/testsuite/lib/target-supports.exp +++ b/gcc/testsuite/lib/target-supports.exp @@ -1390,7 +1390,7 @@ proc check_effective_target_shared { } { # here to be undefined. set extra_flags "" if { [istarget *-*-darwin\[912\]*] } { - set extra_flags "-Wl,-U,_foo,-U,_bar" + set extra_flags "-Wl,-U,_foo,-U,_bar,-U,__Z3foov" } # Note that M68K has a multilib that supports -fpic but not # -fPIC, so we need to check both. We test with a program that The question is: will this reveal new issues in other tests that weren't running before. I'm starting a new regtest and will post the results here.
next prev parent reply other threads:[~2024-03-07 14:25 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-05 7:24 [Bug target/114233] New: " fxcoudert at gcc dot gnu.org 2024-03-05 7:25 ` [Bug target/114233] " fxcoudert at gcc dot gnu.org 2024-03-06 20:32 ` iains at gcc dot gnu.org 2024-03-07 13:31 ` fxcoudert at gcc dot gnu.org 2024-03-07 14:25 ` fxcoudert at gcc dot gnu.org [this message] 2024-03-07 15:06 ` iains at gcc dot gnu.org 2024-03-07 15:45 ` iains at gcc dot gnu.org 2024-03-08 14:19 ` cvs-commit at gcc dot gnu.org 2024-03-29 18:55 ` 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-114233-4-MXq7xAuP5d@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).