https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108500
--- Comment #17 from dhekir at gmail dot com --- To be honest, the "real" test case is very similar to the last one I sent: it's a semi-generated code, with some initialization of the data in the beginning, and then a lot of statements which perform not necessarily useful operations, and in the end a few assertions are checked (e.g. that the initialized data was not tampered with). So, in reality, I expected GCC to discard most of the program after optimization and execute it almost instantly. When I encountered the segmentation fault during compilation, I thought it might also be relevant for other users, so I submitted the bug. Now, however, that the issue is mostly a "performance" issue, it's less likely that other users will encounter such a huge program with "useful" purposes, so I understand completely if you decide this is just not interesting/useful enough. To be honest, I tried compiling the code with other open source C compilers (Clang, and another not-so-mature one), and one failed with a stack overflow, and the other didn't complete until 1h30m, so I terminated it. So, the simple fact that you were able to succesfully compile it with those options is already very interesting to me and sufficient for my "real" test case.
