public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/112652] New: g++.dg/cpp26/literals2.C FAILs
Date: Tue, 21 Nov 2023 15:04:59 +0000 [thread overview]
Message-ID: <bug-112652-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112652
Bug ID: 112652
Summary: g++.dg/cpp26/literals2.C FAILs
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: jakub at gcc dot gnu.org
Target Milestone: ---
Host: *-*-solaris2.11
Target: *-*-solaris2.11
Build: *-*-solaris2.11
The g++.dg/cpp26/literals2.C test FAILs on Solaris, both SPARC and x86:
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++14 (test for errors, line 10)
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++14 (test for errors, line 11)
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++14 (test for errors, line 13)
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++14 (test for errors, line 41)
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++14 (test for errors, line 42)
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++14 (test for errors, line 44)
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++17 (test for errors, line 10)
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++17 (test for errors, line 11)
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++17 (test for errors, line 13)
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++17 (test for errors, line 41)
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++17 (test for errors, line 42)
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++17 (test for errors, line 44)
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++20 (test for errors, line 10)
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++20 (test for errors, line 11)
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++20 (test for errors, line 13)
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++20 (test for errors, line 41)
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++20 (test for errors, line 42)
+FAIL: g++.dg/cpp26/literals2.C -std=gnu++20 (test for errors, line 44)
I initially thought that were due to make check being run with LANG=C, but I
get the same errors with LANG=en_US.UTF-8.
next reply other threads:[~2023-11-21 15:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 15:04 ro at gcc dot gnu.org [this message]
2023-11-21 15:05 ` [Bug c++/112652] " ro at gcc dot gnu.org
2023-11-21 18:32 ` jakub at gcc dot gnu.org
2023-11-22 15:09 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-11-22 15:26 ` jakub at gcc dot gnu.org
2023-11-24 9:05 ` jakub at gcc dot gnu.org
2024-03-12 15:51 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-03-13 13:22 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-03-13 13:46 ` jakub at gcc dot gnu.org
2024-03-13 14:59 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-03-13 15:45 ` jakub at gcc dot gnu.org
2024-03-22 13:52 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-07 7:42 ` rguenth 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-112652-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).