public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/108235] FAIL: g++.dg/compat/abi/bitfield1 cp_compat_x_tst.o-cp_compat_y_tst.o link
Date: Thu, 29 Dec 2022 15:55:18 +0000 [thread overview]
Message-ID: <bug-108235-4-lWlRj8M5cW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108235-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108235
John David Anglin <danglin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jwakely.gcc at gmail dot com
--- Comment #1 from John David Anglin <danglin at gcc dot gnu.org> ---
bash-5.1$ find . -name '*.o'|xargs /opt/gnu64/bin/nm -AC|grep atomic
./src/c++98/pool_allocator.o: U __gnu_cxx::__atomic_add(int
volatile*, int)
./src/c++98/mt_allocator.o: U __gnu_cxx::__atomic_add(int
volatile*, int)
./src/c++98/ios_failure.o: U __gnu_cxx::__atomic_add(int
volatile*, int)
./src/c++98/ios_init.o: U __gnu_cxx::__atomic_add(int
volatile*, int)
./src/c++98/locale_init.o: U __gnu_cxx::__atomic_add(int
volatile*, int)
./src/c++98/locale.o: U __gnu_cxx::__atomic_add(int volatile*,
int)
./src/c++98/localename.o: U __gnu_cxx::__atomic_add(int
volatile*, int)
./src/c++98/stdexcept.o: U __gnu_cxx::__atomic_add(int
volatile*, int)
./src/c++98/messages_members_cow.o: U
__gnu_cxx::__atomic_add(int volatile*, int)
./src/c++11/cow-stdexcept.o: U __gnu_cxx::__atomic_add(int
volatile*, int)
./src/c++11/ios-inst.o: U __gnu_cxx::__atomic_add(int
volatile*, int)
./src/c++11/cow-locale_init.o: U __gnu_cxx::__atomic_add(int
volatile*, int)
./src/c++11/cow-shim_facets.o: U __gnu_cxx::__atomic_add(int
volatile*, int)
./src/c++11/cxx11-shim_facets.o: U __gnu_cxx::__atomic_add(int
volatile*, int)
./src/c++11/cow-string-inst.o: U __gnu_cxx::__atomic_add(int
volatile*, int)
./src/c++11/cow-wstring-inst.o: U __gnu_cxx::__atomic_add(int
volatile*, int)
./src/c++17/fs_dir.o: U __gnu_cxx::__atomic_add(int volatile*,
int)
./src/c++17/fs_ops.o: U __gnu_cxx::__atomic_add(int volatile*,
int)
./src/c++17/cow-fs_dir.o: U __gnu_cxx::__atomic_add(int
volatile*, int)
./src/c++17/cow-fs_ops.o: U __gnu_cxx::__atomic_add(int
volatile*, int)
./src/c++17/cow-fs_path.o: U __gnu_cxx::__atomic_add(int
volatile*, int)
./src/c++20/tzdb.o: U __gnu_cxx::__atomic_add(int volatile*,
int)
./src/c++20/tzdb.o:0000000000000000 t void
std::__atomic_notify_address<int>(int const*, bool) [clone .isra.0]
./src/c++20/tzdb.o:0000000000000000 W void std::__atomic_wait_address_v<int,
std::__atomic_base<int>::wait(int, std::memory_order) const::{lambda()#1}>(int
const*, int, std::__atomic_base<int>::wait(int, std::memory_order)
const::{lambda()#1})
./src/c++20/tzdb.o: U __atomic_compare_exchange_4
./src/c++20/tzdb.o: U __atomic_compare_exchange_8
./src/c++20/tzdb.o: U __atomic_exchange_8
./src/c++20/tzdb.o: U __atomic_fetch_add_4
./src/c++20/tzdb.o: U __atomic_fetch_add_8
./src/c++20/tzdb.o: U __atomic_fetch_sub_8
[...]
I believe the direct use of the above atomic symbols was introduced in the
following change:
commit 9fc61d45fa15fdd3b084d30998ecda164af33e95
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Thu Dec 22 00:37:54 2022 +0000
libstdc++: Implement C++20 time zone support in <chrono>
I have the following patch to work around PR 108228:
diff --git a/libstdc++-v3/src/c++20/tzdb.cc b/libstdc++-v3/src/c++20/tzdb.cc
index 2a4e213d3d9..92752242096 100644
--- a/libstdc++-v3/src/c++20/tzdb.cc
+++ b/libstdc++-v3/src/c++20/tzdb.cc
@@ -64,8 +64,8 @@ namespace __gnu_cxx
#else
[[gnu::weak]] const char* zoneinfo_dir_override();
-#ifdef __APPLE__
- // Need a weak definition for Mach-O.
+#if defined(__APPLE__) || defined(__hpux__)
+ // Need a weak definition for Mach-O and HP-UX.
[[gnu::weak]] const char* zoneinfo_dir_override()
{ return _GLIBCXX_ZONEINFO_DIR; }
#endif
next prev parent reply other threads:[~2022-12-29 15:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 14:43 [Bug libstdc++/108235] New: " danglin at gcc dot gnu.org
2022-12-29 15:55 ` danglin at gcc dot gnu.org [this message]
2022-12-29 16:12 ` [Bug libstdc++/108235] " danglin at gcc dot gnu.org
2022-12-29 20:27 ` danglin at gcc dot gnu.org
2022-12-30 17:08 ` redi at gcc dot gnu.org
2022-12-30 17:08 ` redi at gcc dot gnu.org
2023-01-02 17:59 ` danglin at gcc dot gnu.org
2023-01-02 18:17 ` redi at gcc dot gnu.org
2023-01-05 0:51 ` cvs-commit at gcc dot gnu.org
2023-01-05 0:54 ` redi at gcc dot gnu.org
2023-01-05 2:11 ` dave.anglin at bell dot net
2023-01-06 15:01 ` danglin at gcc dot gnu.org
2023-01-06 15:06 ` danglin at gcc dot gnu.org
2023-01-06 16:51 ` redi at gcc dot gnu.org
2023-01-06 21:21 ` cvs-commit at gcc dot gnu.org
2023-01-06 21:22 ` redi at gcc dot gnu.org
2023-01-08 20:47 ` danglin 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-108235-4-lWlRj8M5cW@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: link
Be 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).