* [Bug libgcc/107327] internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930
2022-10-20 6:45 [Bug libgcc/107327] New: internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930 kaploceh at gmail dot com
@ 2022-10-20 7:27 ` kaploceh at gmail dot com
2022-10-20 9:25 ` [Bug c++/107327] " rguenth at gcc dot gnu.org
` (10 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: kaploceh at gmail dot com @ 2022-10-20 7:27 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107327
--- Comment #1 from Carlos E <kaploceh at gmail dot com> ---
I haven't had any problems compiling it with Make before, usually it goes into:
g++ -O3 -pedantic -std=c++2a -g -Wall -Wextra -Wno-unused-parameter
-Wno-sign-compare -Wno-address -Wno-init-list-lifetime -MD -MP -MF <file.d> -c
-o <file.o> <file.cc>
with the variable CXXFLAGS += -pedantic -std=c++2a -g -Wall -Wextra
-Wno-unused-parameter -Wno-sign-compare -Wno-address from the Makefile
and so on
But this time around, it stops right with the message
internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930
It finishes by telling me to
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
while GNU Make says
Once you have a precise problem you can report it in one of two ways.
Either send electronic mail to:
bug-make@gnu.org
or use our Web-based project management tool, at:
http://savannah.gnu.org/projects/make/
So I'm reporting it here rather than over there.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug c++/107327] internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930
2022-10-20 6:45 [Bug libgcc/107327] New: internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930 kaploceh at gmail dot com
2022-10-20 7:27 ` [Bug libgcc/107327] " kaploceh at gmail dot com
@ 2022-10-20 9:25 ` rguenth at gcc dot gnu.org
2022-10-21 7:43 ` kaploceh at gmail dot com
` (9 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: rguenth at gcc dot gnu.org @ 2022-10-20 9:25 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107327
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2022-10-20
Component|libgcc |c++
Status|UNCONFIRMED |WAITING
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Please attach preprocessed source and maybe try GCC 10.4 which contains many
bugfixes.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug c++/107327] internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930
2022-10-20 6:45 [Bug libgcc/107327] New: internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930 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
` (8 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: kaploceh at gmail dot com @ 2022-10-21 7:43 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107327
--- Comment #3 from Carlos E <kaploceh at gmail dot com> ---
(In reply to Richard Biener from comment #2)
> Please attach preprocessed source and maybe try GCC 10.4 which contains many
> bugfixes.
I downloaded GCC 10.4 and it's compiling now. Will try it out. Thanks.
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?
Is it g++ with an -E option? Are other options relevant? Or GNU Make -d ?
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug c++/107327] internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930
2022-10-20 6:45 [Bug libgcc/107327] New: internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930 kaploceh at gmail dot com
` (2 preceding siblings ...)
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
` (7 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: marxin at gcc dot gnu.org @ 2022-10-21 8:06 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107327
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
> 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.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug c++/107327] internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930
2022-10-20 6:45 [Bug libgcc/107327] New: internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930 kaploceh at gmail dot com
` (3 preceding siblings ...)
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
` (6 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: kaploceh at gmail dot com @ 2022-10-21 8:37 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107327
--- Comment #5 from Carlos E <kaploceh at gmail dot com> ---
Created attachment 53743
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53743&action=edit
internal compiler error: in tsubst_pack_expansion
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug c++/107327] internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930
2022-10-20 6:45 [Bug libgcc/107327] New: internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930 kaploceh at gmail dot com
` (4 preceding siblings ...)
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
` (5 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: kaploceh at gmail dot com @ 2022-10-21 8:42 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107327
--- Comment #6 from Carlos E <kaploceh at gmail dot com> ---
(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. I can also attach if necessary the whole file generated by GNU Make -d
Still compiling gcc 10.4. It'll have to be postponed.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug c++/107327] internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930
2022-10-20 6:45 [Bug libgcc/107327] New: internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930 kaploceh at gmail dot com
` (5 preceding siblings ...)
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
` (4 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: marxin at gcc dot gnu.org @ 2022-10-21 10:40 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107327
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> ---
(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
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug c++/107327] internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930
2022-10-20 6:45 [Bug libgcc/107327] New: internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930 kaploceh at gmail dot com
` (6 preceding siblings ...)
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
` (3 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: kaploceh at gmail dot com @ 2022-10-23 15:16 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107327
--- Comment #8 from Carlos E <kaploceh at gmail dot com> ---
Created attachment 53762
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53762&action=edit
preprocessed file
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug c++/107327] internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930
2022-10-20 6:45 [Bug libgcc/107327] New: internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930 kaploceh at gmail dot com
` (7 preceding siblings ...)
2022-10-23 15:16 ` kaploceh at gmail dot com
@ 2022-10-23 15:19 ` kaploceh at gmail dot com
2022-10-24 8:11 ` marxin at gcc dot gnu.org
` (2 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: kaploceh at gmail dot com @ 2022-10-23 15:19 UTC (permalink / raw)
To: gcc-bugs
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
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug c++/107327] internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930
2022-10-20 6:45 [Bug libgcc/107327] New: internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930 kaploceh at gmail dot com
` (8 preceding siblings ...)
2022-10-23 15:19 ` kaploceh at gmail dot com
@ 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
11 siblings, 0 replies; 13+ messages in thread
From: marxin at gcc dot gnu.org @ 2022-10-24 8:11 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107327
--- Comment #10 from Martin Liška <marxin at gcc dot gnu.org> ---
Can't reproduce the ICE with any GCC release I have:
gcc-bisect.py 'g++ -O3 -pedantic -std=c++2a -g -Wall -Wextra
-Wno-unused-parameter -Wno-sign-compare -Wno-address -Wno-init-list-lifetime
pr107327.ii -c'
Releases
10.1.0 (6e6e3f144a33ae50)(07 May 2020 10:50): [took: 0.02 s] result: OK
10.2.0 (ee5c3db6c5b2c333)(23 Jul 2020 06:35): [took: 0.01 s] result: OK
10.3.0 (f00b5710a30f22ef)(08 Apr 2021 11:56): [took: 0.01 s] result: OK
10.4.0 (7ff47281ce4f3699)(28 Jun 2022 08:37): [took: 0.02 s] result: OK
11.1.0 (50bc9185c2821350)(27 Apr 2021 11:39): [took: 0.02 s] result: OK
11.2.0 (7ca388565af176bd)(28 Jul 2021 06:55): [took: 0.02 s] result: OK
11.3.0 (2d280e7eafc086e9)(21 Apr 2022 07:59): [took: 0.02 s] result: OK
12.1.0 (1ea978e3066ac565)(06 May 2022 07:07): [took: 0.02 s] result: OK
12.2.0 (2ee5e4300186a92a)(19 Aug 2022 08:10): [took: 0.02 s] result: OK
13.0 (6bfea64164c3f198)(24 Oct 2022 10:31): [took: 0.02 s] result: OK
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug c++/107327] internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930
2022-10-20 6:45 [Bug libgcc/107327] New: internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930 kaploceh at gmail dot com
` (9 preceding siblings ...)
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
11 siblings, 0 replies; 13+ messages in thread
From: kaploceh at gmail dot com @ 2022-11-04 22:20 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107327
--- Comment #11 from Carlos E <kaploceh at gmail dot com> ---
Created attachment 53829
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53829&action=edit
preprocessed file on 10.2
preprocessed with echo '#include <stdio.h>' | gcc -x c - -E
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug c++/107327] internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930
2022-10-20 6:45 [Bug libgcc/107327] New: internal compiler error: in tsubst_pack_expansion, at cp/pt.c:12930 kaploceh at gmail dot com
` (10 preceding siblings ...)
2022-11-04 22:20 ` kaploceh at gmail dot com
@ 2022-11-08 14:21 ` marxin at gcc dot gnu.org
11 siblings, 0 replies; 13+ messages in thread
From: marxin at gcc dot gnu.org @ 2022-11-08 14:21 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107327
--- Comment #12 from Martin Liška <marxin at gcc dot gnu.org> ---
Can't reproduce :/
^ permalink raw reply [flat|nested] 13+ messages in thread