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++/114103] New: FAIL: 29_atomics/atomic/lock_free_aliases.cc -std=gnu++20 (test for excess errors) Date: Sun, 25 Feb 2024 17:47:49 +0000 [thread overview] Message-ID: <bug-114103-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114103 Bug ID: 114103 Summary: FAIL: 29_atomics/atomic/lock_free_aliases.cc -std=gnu++20 (test for excess errors) Product: gcc Version: 14.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/xg++ -shared-libgcc -B/ho me/dave/gnu/gcc/objdir64/./gcc -nostdinc++ -L/home/dave/gnu/gcc/objdir64/hppa64- hp-hpux11.11/libstdc++-v3/src -L/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/ libstdc++-v3/src/.libs -L/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc ++-v3/libsupc++/.libs -B/opt/gnu64/gcc/gcc-14/hppa64-hp-hpux11.11/bin/ -B/opt/gn u64/gcc/gcc-14/hppa64-hp-hpux11.11/lib/ -isystem /opt/gnu64/gcc/gcc-14/hppa64-hp -hpux11.11/include -isystem /opt/gnu64/gcc/gcc-14/hppa64-hp-hpux11.11/sys-includ e -fchecking=1 -B/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/./libstdc++-v3/ src/.libs -fmessage-length=0 -fno-show-column -ffunction-sections -fdata-section s -O2 -g -DLOCALEDIR="." -nostdinc++ -I/home/dave/gnu/gcc/objdir64/hppa64-hp-hpu x11.11/libstdc++-v3/include/hppa64-hp-hpux11.11 -I/home/dave/gnu/gcc/objdir64/hppa64-hp-hpux11.11/libstdc++-v3/include -I/home/dave/gnu/gcc/gcc/libstdc++-v3/libsupc++ -I/home/dave/gnu/gcc/gcc/libstdc++-v3/include/backward -I/home/dave/gnu/gcc/gcc/libstdc++-v3/testsuite/util /home/dave/gnu/gcc/gcc/libstdc++-v3/testsuite/29_atomics/atomic/lock_free_aliases.cc -std=gnu++20 -D__GLIBCXX__=99999999 -fdiagnostics-plain-output -S -o lock_free_aliases.s /home/dave/gnu/gcc/gcc/libstdc++-v3/testsuite/29_atomics/atomic/lock_free_aliases.cc:33: error: static assertion failed /home/dave/gnu/gcc/gcc/libstdc++-v3/testsuite/29_atomics/atomic/lock_free_aliases.cc:34: error: static assertion failed compiler exited with status 1 FAIL: 29_atomics/atomic/lock_free_aliases.cc -std=gnu++20 (test for excess errors) Excess errors: /home/dave/gnu/gcc/gcc/libstdc++-v3/testsuite/29_atomics/atomic/lock_free_aliases.cc:33: error: static assertion failed /home/dave/gnu/gcc/gcc/libstdc++-v3/testsuite/29_atomics/atomic/lock_free_aliases.cc:34: error: static assertion failed
next reply other threads:[~2024-02-25 17:47 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-25 17:47 danglin at gcc dot gnu.org [this message] 2024-02-26 10:54 ` [Bug libstdc++/114103] " redi at gcc dot gnu.org 2024-02-26 10:55 ` redi at gcc dot gnu.org 2024-02-26 10:56 ` redi at gcc dot gnu.org 2024-02-26 12:21 ` dave.anglin at bell dot net 2024-02-26 12:22 ` redi at gcc dot gnu.org 2024-02-26 12:25 ` dave.anglin at bell dot net 2024-02-27 14:32 ` redi at gcc dot gnu.org 2024-02-27 20:49 ` dave.anglin at bell dot net 2024-02-28 1:04 ` dave.anglin at bell dot net 2024-02-28 9:31 ` redi at gcc dot gnu.org 2024-02-29 17:44 ` redi at gcc dot gnu.org 2024-03-01 22:15 ` dave.anglin at bell dot net 2024-03-01 22:35 ` redi at gcc dot gnu.org 2024-03-01 22:38 ` redi at gcc dot gnu.org 2024-03-01 22:42 ` redi at gcc dot gnu.org 2024-03-02 23:36 ` dave.anglin at bell dot net 2024-03-07 21:00 ` cvs-commit at gcc dot gnu.org 2024-03-07 21:01 ` redi at gcc dot gnu.org 2024-03-23 18:12 ` 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-114103-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).