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] New: FAIL: g++.dg/compat/abi/bitfield1 cp_compat_x_tst.o-cp_compat_y_tst.o link
Date: Tue, 27 Dec 2022 14:43:29 +0000 [thread overview]
Message-ID: <bug-108235-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108235
Bug ID: 108235
Summary: FAIL: g++.dg/compat/abi/bitfield1
cp_compat_x_tst.o-cp_compat_y_tst.o link
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: danglin at gcc dot gnu.org
Target Milestone: ---
Host: hppa64-hp-hpux11.11
Target: hppa64-hp-hpux11.11
Build: hppa64-hp-hpux11.11
spawn -ignore SIGHUP /home/dave/gnu/gcc/objdir64/gcc/testsuite/g++/../../xg++
-B
/home/dave/gnu/gcc/objdir64/gcc/testsuite/g++/../../ cp_compat_main_tst.o
cp_com
pat_x_tst.o cp_compat_y_tst.o -fdiagnostics-plain-output -nostdinc++
-I/home/dav
e/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc++-v3/include/hppa64-hp-hpux11.11
-I/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc++-v3/include
-I/home/d
ave/gnu/gcc/gcc/libstdc++-v3/libsupc++
-I/home/dave/gnu/gcc/gcc/libstdc++-v3/inc
lude/backward -I/home/dave/gnu/gcc/gcc/libstdc++-v3/testsuite/util
-fmessage-len
gth=0 -w -ansi -pedantic-errors -funsigned-bitfields
-L/home/dave/gnu/gcc/objdir
64/hppa64-hp-hpux11.11/./libstdc++-v3/src/.libs
-B/home/dave/gnu/gcc/objdir64/hp
pa64-hp-hpux11.11/./libstdc++-v3/src/.libs
-L/home/dave/gnu/gcc/objdir64/hppa64-
hp-hpux11.11/./libstdc++-v3/src/.libs
-L/home/dave/gnu/gcc/objdir64/hppa64-hp-hp
ux11.11/./libstdc++-v3/src/experimental/.libs -lm -o
g++-dg-compat-abi-bitfield1
-01.exe
ld: (Warning) Unsatisfied symbol "__atomic_fetch_add_4" in file
/home/dave/gnu/g
cc/objdir64/hppa64-hp-hpux11.11/./libstdc++-v3/src/.libs/libstdc++.sl
ld: (Warning) Unsatisfied symbol "__atomic_fetch_add_8" in file
/home/dave/gnu/g
cc/objdir64/hppa64-hp-hpux11.11/./libstdc++-v3/src/.libs/libstdc++.sl
ld: (Warning) Unsatisfied symbol "__atomic_compare_exchange_4" in file
/home/dav
e/gnu/gcc/objdir64/hppa64-hp-hpux11.11/./libstdc++-v3/src/.libs/libstdc++.sl
ld: (Warning) Unsatisfied symbol "__atomic_compare_exchange_8" in file
/home/dav
e/gnu/gcc/objdir64/hppa64-hp-hpux11.11/./libstdc++-v3/src/.libs/libstdc++.sl
ld: (Warning) Unsatisfied symbol "__atomic_fetch_sub_8" in file
/home/dave/gnu/g
cc/objdir64/hppa64-hp-hpux11.11/./libstdc++-v3/src/.libs/libstdc++.sl
ld: (Warning) Unsatisfied symbol "__atomic_exchange_8" in file
/home/dave/gnu/gc
c/objdir64/hppa64-hp-hpux11.11/./libstdc++-v3/src/.libs/libstdc++.sl
6 warnings.
FAIL: g++.dg/compat/abi/bitfield1 cp_compat_x_tst.o-cp_compat_y_tst.o link
I believe libstdc++ needs to be linked against libatomic to provide these
symbols.
This might affect also affect linux target.
next reply other threads:[~2022-12-27 14:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 14:43 danglin at gcc dot gnu.org [this message]
2022-12-29 15:55 ` [Bug libstdc++/108235] " danglin at gcc dot gnu.org
2022-12-29 16:12 ` 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@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).