public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/112269] [14 Regression] x86_64 GNU/Linux '-m32' multilib 'libstdc++-v3/include/complex:1493: internal compiler error: in tsubst_expr, at cp/pt.cc:21534' since r14-4796-g3e3d73ed5e85e7
Date: Sat, 04 Nov 2023 08:28:48 +0000 [thread overview]
Message-ID: <bug-112269-4-MbRBGqv4RV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112269-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112269
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Patrick Palka from comment #5)
> I can't reproduce any of these testsuite failures on trunk with x86_64
> -m32... could you provide a preprocessed source file perhaps?
The libstdc++ testsuite shows lots of failures with -m32 -std=c++20
e.g.
FAIL: 23_containers/vector/48101-2_neg.cc -std=c++20 (test for errors, line )
FAIL: 23_containers/vector/48101-2_neg.cc -std=c++20 (test for excess errors)
Excess errors:
/tmp/build/x86_64-pc-linux-gnu/32/libstdc++-v3/include/complex:1493: internal
compiler error: in tsubst_expr, at cp/pt.cc:21534
0x78b9fb tsubst_expr(tree_node*, tree_node*, int, tree_node*)
/home/test/src/gcc/gcc/cp/pt.cc:21534
next prev parent reply other threads:[~2023-11-04 8:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 20:52 [Bug c++/112269] New: [14 Regression] x86_64 GNU/Linux '-m32' multilib 'libstdc++-v3/include/complex:1493: internal compiler error: in tsubst_expr, at cp/pt.cc:21534' tschwinge at gcc dot gnu.org
2023-10-28 21:03 ` [Bug c++/112269] " pinskia at gcc dot gnu.org
2023-10-28 21:04 ` pinskia at gcc dot gnu.org
2023-10-29 8:37 ` schwab@linux-m68k.org
2023-10-29 9:46 ` schwab@linux-m68k.org
2023-10-29 16:33 ` [Bug c++/112269] [14 Regression] x86_64 GNU/Linux '-m32' multilib 'libstdc++-v3/include/complex:1493: internal compiler error: in tsubst_expr, at cp/pt.cc:21534' since r14-4796-g3e3d73ed5e85e7 pinskia at gcc dot gnu.org
2023-10-30 16:19 ` ppalka at gcc dot gnu.org
2023-10-31 8:17 ` tschwinge at gcc dot gnu.org
2023-10-31 14:58 ` ppalka at gcc dot gnu.org
2023-11-03 7:34 ` pinskia at gcc dot gnu.org
2023-11-03 8:30 ` rguenth at gcc dot gnu.org
2023-11-04 8:28 ` redi at gcc dot gnu.org [this message]
2023-11-04 18:56 ` pinskia at gcc dot gnu.org
2023-11-07 17:20 ` ppalka at gcc dot gnu.org
2023-11-15 17:03 ` cvs-commit at gcc dot gnu.org
2023-11-15 17:05 ` ppalka at gcc dot gnu.org
2023-11-24 16:56 ` cvs-commit at gcc dot gnu.org
2023-11-27 22:02 ` cvs-commit 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-112269-4-MbRBGqv4RV@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).