public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/100179] [12 regression] xtreme-header-2_a.H fails on arm-eabi
Date: Wed, 21 Apr 2021 11:55:32 +0000 [thread overview]
Message-ID: <bug-100179-4-8Z3dEkIT4c@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100179-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100179
--- Comment #1 from Christophe Lyon <clyon at gcc dot gnu.org> ---
Similar errors noticed in libstdc++ testsuite:
17_intro/headers/c++2020/all_attributes.cc (test for excess errors)
17_intro/headers/c++2020/all_no_exceptions.cc (test for excess errors)
17_intro/headers/c++2020/all_no_rtti.cc (test for excess errors)
17_intro/headers/c++2020/all_pedantic_errors.cc (test for excess errors)
17_intro/headers/c++2020/operator_names.cc (test for excess errors)
17_intro/headers/c++2020/stdc++.cc (test for excess errors)
17_intro/headers/c++2020/stdc++_multiple_inclusion.cc (test for excess
errors)
20_util/polymorphic_allocator/allocate_object.cc (test for excess errors)
20_util/polymorphic_allocator/construct_c++2a.cc (test for excess errors)
20_util/polymorphic_allocator/lwg3237.cc (test for excess errors)
20_util/scoped_allocator/construct_pair_c++2a.cc (test for excess errors)
20_util/uses_allocator/make_obj.cc (test for excess errors)
21_strings/basic_string/hash/hash_char8_t.cc (test for excess errors)
24_iterators/normal_iterator/cmp_c++20.cc (test for excess errors)
27_io/basic_istringstream/cons/char/1.cc (test for excess errors)
27_io/basic_istringstream/cons/wchar_t/1.cc (test for excess errors)
27_io/basic_istringstream/str/char/2.cc (test for excess errors)
27_io/basic_istringstream/str/wchar_t/2.cc (test for excess errors)
27_io/basic_ostringstream/cons/char/1.cc (test for excess errors)
27_io/basic_ostringstream/cons/wchar_t/1.cc (test for excess errors)
27_io/basic_ostringstream/str/char/3.cc (test for excess errors)
27_io/basic_ostringstream/str/wchar_t/3.cc (test for excess errors)
27_io/basic_stringbuf/cons/char/2.cc (test for excess errors)
27_io/basic_stringbuf/cons/wchar_t/2.cc (test for excess errors)
27_io/basic_stringbuf/str/char/4.cc (test for excess errors)
27_io/basic_stringbuf/str/wchar_t/4.cc (test for excess errors)
27_io/basic_stringstream/cons/char/1.cc (test for excess errors)
27_io/basic_stringstream/cons/wchar_t/1.cc (test for excess errors)
27_io/basic_stringstream/str/char/5.cc (test for excess errors)
27_io/basic_stringstream/str/wchar_t/5.cc.cc (test for excess errors)
27_io/basic_syncbuf/basic_ops/1.cc (test for excess errors)
27_io/basic_syncstream/basic_ops/1.cc (test for excess errors)
next prev parent reply other threads:[~2021-04-21 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 11:54 [Bug libstdc++/100179] New: " clyon at gcc dot gnu.org
2021-04-21 11:55 ` clyon at gcc dot gnu.org [this message]
2021-04-21 14:26 ` [Bug libstdc++/100179] " redi at gcc dot gnu.org
2021-04-22 12:59 ` cvs-commit at gcc dot gnu.org
2021-04-22 13:37 ` cvs-commit at gcc dot gnu.org
2021-04-22 13:38 ` redi at gcc dot gnu.org
2021-04-23 8:36 ` clyon at gcc dot gnu.org
2021-04-23 8:41 ` 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-100179-4-8Z3dEkIT4c@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).