https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96197
Joe Burzinski <tridacnid at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tridacnid at gmail dot com
--- Comment #6 from Joe Burzinski <tridacnid at gmail dot com> ---
gcc 8.3.1
I just ran into almost this exact scenario. We use constexpr for catching
inconsistencies at compile time and a recent conversion of 50ish arrays of 100
elements takes an unknown amount of time to compile (I killed the build as I
ate into my last GB of swap) and used ~46GB of RAM + ~16GB of swap. I'm unable
to test on a later version of gcc but plugging the test case into godbolt
compiles on clang but runs out of memory when using gcc 10.1 and trunk.
I was able to trim the case down to get it to a compile time of 33s using ~24GB
of memory. The same trimmed down case compiles in less than a second and a
couple hundred MB of memory with clang10 for comparison.
