[Bug c/84183] internal compiler error: in initialize, at alloc-pool.h:257

[tplank at gmx dot at]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84183

--- Comment #5 from Thomas Plank  ---
(In reply to Thomas Plank from comment #4)
> I'm pretty sure I already had binutils updated to 2.30.
> 
> I will give it a try with a downgrade to 2.29.1 and check if gcc 7.3.0
> builds then.

I didn't do the downgrade but used the patched binutils version.

GCC now builds under cygwin, see below:

$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-unknown-cygwin/7.3.0/lto-wrapper.exe
Target: x86_64-unknown-cygwin
Configured with: ../gcc-7.3.0/configure --enable-threads
--enable-languages=c,c++,fortran,lto,objc,obj-c++ --disable-sjlj-exceptions
--with-mpc=/usr/local --with-isl=/usr/local --with-mpfr=/usr/local
--with-gmp=/usr/local
Thread model: posix
gcc version 7.3.0 (GCC)

[Bug c/84183] internal compiler error: in initialize, at alloc-pool.h:257

[tplank at gmx dot at]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84183

--- Comment #4 from Thomas Plank  ---
I'm pretty sure I already had binutils updated to 2.30.

I will give it a try with a downgrade to 2.29.1 and check if gcc 7.3.0 builds
then.

[Bug c/84183] internal compiler error: in initialize, at alloc-pool.h:257

[dmalcolm at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84183

--- Comment #3 from David Malcolm  ---
(In reply to Andre Pribil from comment #2)
Thanks.  Sounds like this might be an ld bug then.

Thomas: do you know which version of binutils you were using?

[Bug c/84183] internal compiler error: in initialize, at alloc-pool.h:257

[a.pri...@beck-ipc.com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84183

Andre Pribil  changed:

   What|Removed |Added

 CC||a.pri...@beck-ipc.com

--- Comment #2 from Andre Pribil  ---

I had the same assert message when running a freshly build GCC 7.3.0
(i686-w64-mingw32). However, I also did get the same message when I build a GCC
7.2.0 or even older version.

Finally, it turned out that not the GCC version was the problem here.
It seems that usage of binutils 2.30 is responsible for this problem. Using
binutils 2.29.1 did fix it.

This binutils problem is already fixed now, see here:
https://sourceware.org/bugzilla/show_bug.cgi?id=22762

[Bug c/84183] internal compiler error: in initialize, at alloc-pool.h:257

[dmalcolm at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84183

David Malcolm  changed:

   What|Removed |Added

 CC||dmalcolm at gcc dot gnu.org

--- Comment #1 from David Malcolm  ---
Thanks for filing this bug report.

Looks like it's failing in "s-selftest", running the selftests within cc1. 
These ought to be a no-op for a release build, so presumably it's just
happening to fail the first time that the newly built cc1 is run.

Line 257 of alloc-pool.h is:

  gcc_checking_assert (m_name);

within base_pool_allocator ::initialize (), so presumably
m_name is NULL  ...somehow.