[Bug preprocessor/96391] [10/11 Regression] internal compiler error: in linemap_compare_locations, at libcpp/line-map.c:1359

2020-12-05 Thread mike at cchtml dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96391

--- Comment #8 from Michael Cronenworth  ---
(In reply to Jan Smets from comment #5)
> Similar issue @ https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96935

I applied the patch from that bug but it did not fix this issue.

Anything I can do to help push this bug along?

[Bug preprocessor/96391] [10/11 Regression] internal compiler error: in linemap_compare_locations, at libcpp/line-map.c:1359

2021-02-09 Thread mike at cchtml dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96391

--- Comment #12 from Michael Cronenworth  ---
(In reply to David Malcolm from comment #11)
> FWIW I had another go at reproduing this, but after various failures due to
> running out of disk space, I was able to rebuild the SRPM from comment #0
> without seeing the crash, via:
Yes, and with -save-temps you double the disk space required. :(

>   mock --rebuild mingw-wine-gecko-2.47.1-2.fc32.src.rpm -N -r fedora-32-i386

That's a reasonable mock command for a Fedora 32 build.

> (which the root.log tells me used gcc-c++-10.2.1-9.fc32.i686.rpm).

That's the Linux GCC. You will want to see the version for MinGW:
mingw-gcc-9.2.1-6.fc32 - which does not crash so I'm not surprised you didn't
crash.

> Michael: is that the mock configuration that's failing for you, or are you
> using a different one?

Try: mock --rebuild mingw-wine-gecko-2.47.1-2.fc32.src.rpm -N -r fedora-33-i386

It's still failing for me today. I'm working around it by passing -save-temps
to CFLAGS as packages that fail to compile in Fedora for too long are dropped
from the distribution.

[Bug preprocessor/96391] [10 Regression] ICE in linemap_compare_locations on "CONST VOID" in large C++ files

2022-01-25 Thread mike at cchtml dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96391

--- Comment #27 from Michael Cronenworth  ---
I can also say that gcc 11 has fixed this. Thanks. I'm happy to close as I will
not be using 10.x anymore.