public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kaploceh at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107327] internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930
Date: Sun, 23 Oct 2022 15:19:51 +0000 [thread overview]
Message-ID: <bug-107327-4-d18KBz94IM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107327-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107327
--- Comment #9 from Carlos E <kaploceh at gmail dot com> ---
(In reply to Martin Liška from comment #7)
> (In reply to Carlos E from comment #6)
> > (In reply to Martin Liška from comment #4)
> > > > When you say to attach a preprocessed source, what would be the most
> > > > accepted command that I should be running which can reliably show whatever
> > > > was preprocessed?
> > >
> > > Just append -E to the existing command line arguments, that would be fine.
> >
> > done.
>
> We need what was likely printed to stdout, or saved to a .o file.
>
> See what's the pre-processed source file:
> echo '#include <stdio.h>' | gcc -x c - -E
thank you Martin.
It did compile as Richard suggested with 10.4
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-pc-linux-gnu/10.4.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ./configure --with-mpc-lib= --disable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.4.0 (GCC)
the preprocessed file was after installing 10.4.
I can revert to 10.2
next prev parent reply other threads:[~2022-10-23 15:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 6:45 [Bug libgcc/107327] New: " kaploceh at gmail dot com
2022-10-20 7:27 ` [Bug libgcc/107327] " kaploceh at gmail dot com
2022-10-20 9:25 ` [Bug c++/107327] " rguenth at gcc dot gnu.org
2022-10-21 7:43 ` kaploceh at gmail dot com
2022-10-21 8:06 ` marxin at gcc dot gnu.org
2022-10-21 8:37 ` kaploceh at gmail dot com
2022-10-21 8:42 ` kaploceh at gmail dot com
2022-10-21 10:40 ` marxin at gcc dot gnu.org
2022-10-23 15:16 ` kaploceh at gmail dot com
2022-10-23 15:19 ` kaploceh at gmail dot com [this message]
2022-10-24 8:11 ` marxin at gcc dot gnu.org
2022-11-04 22:20 ` kaploceh at gmail dot com
2022-11-08 14:21 ` marxin 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-107327-4-d18KBz94IM@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).