public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/107720] New: [13 regression] New C++ library test cases (and many others) in r13-3936-g1d9454aba615ea fail
Date: Wed, 16 Nov 2022 17:46:50 +0000 [thread overview]
Message-ID: <bug-107720-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107720
Bug ID: 107720
Summary: [13 regression] New C++ library test cases (and many
others) in r13-3936-g1d9454aba615ea fail
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:1d9454aba615eadd0d85c93713dd848227345f67, r13-3936-g1d9454aba615ea
This was on a make check of a simple (non-bootstrap) built compiler. I only
see this on one system.
Ubuntu 22.04.1 LTS
gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
FAIL: 17_intro/headers/c++2020/all_attributes.cc (test for excess errors)
FAIL: 17_intro/headers/c++2020/all_no_exceptions.cc (test for excess errors)
FAIL: 17_intro/headers/c++2020/all_no_rtti.cc (test for excess errors)
FAIL: 17_intro/headers/c++2020/all_pedantic_errors.cc (test for excess errors)
FAIL: 17_intro/headers/c++2020/operator_names.cc (test for excess errors)
FAIL: 17_intro/headers/c++2020/stdc++.cc (test for excess errors)
FAIL: 17_intro/headers/c++2020/stdc++_multiple_inclusion.cc (test for excess
errors)
FAIL: std/format/arguments/args.cc (test for excess errors)
FAIL: std/format/error.cc (test for excess errors)
FAIL: std/format/formatter.cc (test for excess errors)
FAIL: std/format/functions/format.cc (test for excess errors)
FAIL: std/format/functions/format_to_n.cc (test for excess errors)
FAIL: std/format/functions/size.cc (test for excess errors)
FAIL: std/format/functions/vformat_to.cc (test for excess errors)
FAIL: std/format/parse_ctx.cc (test for excess errors)
FAIL: std/format/string.cc (test for excess errors)
FAIL: std/format/string_neg.cc (test for excess errors)
FAIL: 17_intro/headers/c++2020/all_no_exceptions.cc (test for excess errors)
Excess errors:
/home/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/format:2566:
error: '_Args_next_value_' was not declared in this scope; did you mean
'_Arg_next_value_'?
/home/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/format:2903:
error: expected ';' before 'else'
/home/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/format:2906:
error: expected ';' before 'else'
/home/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/format:2999:
error: duplicate case value
/home/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/format:3019:
error: duplicate case value
/home/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/format:2999:
error: duplicate case value
/home/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/format:3019:
error: duplicate case value
/home/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/format:1421:
error: call of overloaded 'to_chars(char*&, char*&, __ieee128&,
std::chars_format&, std::size_t&)' is ambiguous
/home/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/format:1423:
error: call of overloaded 'to_chars(char*&, char*&, __ieee128&,
std::chars_format&)' is ambiguous
/home/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/format:1425:
error: call of overloaded 'to_chars(char*&, char*&, __ieee128&)' is ambiguous
/home/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/format:1421:
error: call of overloaded 'to_chars(char*&, char*&, __ieee128&,
std::chars_format&, std::size_t&)' is ambiguous
/home/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/format:1423:
error: call of overloaded 'to_chars(char*&, char*&, __ieee128&,
std::chars_format&)' is ambiguous
/home/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/format:1425:
error: call of overloaded 'to_chars(char*&, char*&, __ieee128&)' is ambiguous
/home/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/format:2999:
error: duplicate case value
/home/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/format:3019:
error: duplicate case value
/home/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/format:2999:
error: duplicate case value
/home/seurer/gcc/git/build/gcc-test2/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/format:3019:
error: duplicate case value
commit 1d9454aba615eadd0d85c93713dd848227345f67 (HEAD, refs/bisect/bad)
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Tue Oct 18 21:20:06 2022 +0100
libstdc++: Implement C++20 <format> [PR104166]
next reply other threads:[~2022-11-16 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 17:46 seurer at gcc dot gnu.org [this message]
2022-11-16 18:51 ` [Bug libstdc++/107720] " redi at gcc dot gnu.org
2022-11-16 20:48 ` redi at gcc dot gnu.org
2022-11-16 20:59 ` cvs-commit at gcc dot gnu.org
2022-11-17 0:34 ` cvs-commit at gcc dot gnu.org
2022-11-17 0:35 ` redi 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-107720-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).