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 libstdc++/112397] New: Two persistent libstdc++ test failures on x86_64-apple-darwin Date: Sun, 05 Nov 2023 20:42:47 +0000 [thread overview] Message-ID: <bug-112397-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112397 Bug ID: 112397 Summary: Two persistent libstdc++ test failures on x86_64-apple-darwin Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: fxcoudert at gcc dot gnu.org Target Milestone: --- FAIL: 17_intro/static.cc -std=gnu++17 (test for excess errors) FAIL: 20_util/to_chars/4.cc -std=gnu++17 (test for excess errors) The both have the same linker warning: ld: warning: direct access in function 'operator new[](unsigned long, std::nothrow_t const&) (.cold)' from file '/Users/fx/ibin-2023 1105/x86_64-apple-darwin21/./libstdc++-v3/src/.libs/libstdc++.a(new_opvnt.o)' to global weak symbol 'operator new[](unsigned long, s td::nothrow_t const&)' from file '/Users/fx/ibin-20231105/x86_64-apple-darwin21/./libstdc++-v3/src/.libs/libstdc++.a(new_opvnt.o)' m eans the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with diff erent visibility settings. ld: warning: direct access in function 'operator new[](unsigned long, std::nothrow_t const&) (.cold)' from file '/Users/fx/ibin-20231105/x86_64-apple-darwin21/./libstdc++-v3/src/.libs/libstdc++.a(new_opvnt.o)' to global weak symbol 'operator new[](unsigned long, std::nothrow_t const&)' from file '/Users/fx/ibin-20231105/x86_64-apple-darwin21/./libstdc++-v3/src/.libs/libstdc++.a(new_opvnt.o)' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings. I am not sure what the "different visibility settings" are, or if it's just a red herring, but the testcase is compiled with: Executing on host: /Users/fx/ibin-20231105/./gcc/xg++ -shared-libgcc -B/Users/fx/ibin-20231105/./gcc -nostdinc++ -L/Users/fx/ibin-20231105/x86_64-apple-darwin21/libstdc++-v3/src -L/Users/fx/ibin-20231105/x86_64-apple-darwin21/libstdc++-v3/src/.libs -L/Users/fx/ibin-20231105/x86_64-apple-darwin21/libstdc++-v3/libsupc++/.libs -B/Users/fx/irun-20231105/x86_64-apple-darwin21/bin/ -B/Users/fx/irun-20231105/x86_64-apple-darwin21/lib/ -isystem /Users/fx/irun-20231105/x86_64-apple-darwin21/include -isystem /Users/fx/irun-20231105/x86_64-apple-darwin21/sys-include -fchecking=1 -B/Users/fx/ibin-20231105/x86_64-apple-darwin21/./libstdc++-v3/src/.libs -fmessage-length=0 -fno-show-column -ffunction-sections -fdata-sections -g -O2 -DLOCALEDIR="." -nostdinc++ -I/Users/fx/ibin-20231105/x86_64-apple-darwin21/libstdc++-v3/include/x86_64-apple-darwin21 -I/Users/fx/ibin-20231105/x86_64-apple-darwin21/libstdc++-v3/include -I/Users/fx/gcc-upstream/libstdc++-v3/libsupc++ -I/Users/fx/gcc-upstream/libstdc++-v3/include/backward -I/Users/fx/gcc-upstream/libstdc++-v3/testsuite/util /Users/fx/gcc-upstream/libstdc++-v3/testsuite/17_intro/static.cc -std=gnu++17 -static-libstdc++ -fdiagnostics-plain-output ./libtestc++.a -liconv -L/Users/fx/ibin-20231105/x86_64-apple-darwin21/libstdc++-v3/src/filesystem/.libs -L/Users/fx/ibin-20231105/x86_64-apple-darwin21/libstdc++-v3/src/experimental/.libs -lm -o ./static.exe (timeout = 360)
next reply other threads:[~2023-11-05 20:42 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-05 20:42 fxcoudert at gcc dot gnu.org [this message] 2023-11-06 9:19 ` [Bug libstdc++/112397] " redi at gcc dot gnu.org 2023-11-06 16:17 ` [Bug target/112397] " iains at gcc dot gnu.org 2024-02-07 17:37 ` iains at gcc dot gnu.org 2024-02-08 12:11 ` redi at gcc dot gnu.org 2024-02-08 12:15 ` redi at gcc dot gnu.org 2024-02-08 12:21 ` jakub at gcc dot gnu.org 2024-02-08 13:12 ` iains at gcc dot gnu.org 2024-02-08 13:18 ` jakub at gcc dot gnu.org 2024-02-08 13:22 ` jakub at gcc dot gnu.org 2024-02-08 14:02 ` iains at gcc dot gnu.org 2024-02-19 20:16 ` cvs-commit at gcc dot gnu.org 2024-04-03 14:57 ` cvs-commit at gcc dot gnu.org 2024-04-21 13:04 ` cvs-commit at gcc dot gnu.org 2024-04-29 14:18 ` cvs-commit at gcc dot gnu.org 2024-04-29 14:42 ` 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-112397-4@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).