https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117291
--- Comment #7 from Peter Bergner <bergner at gcc dot gnu.org> --- (In reply to Richard Biener from comment #5) > I agree it's difficult to solve. GCC tries to up the stack limit to > unlimited, why isn't this working for you? Maybe we should remember the > failure to do so and report that (and make the segfault handler use an > alternate stack ...)? I wasn't aware GCC attempts to up the ulimit value. Do you know where that code is? Does it attempt to do that before compiling the function or as the result of encountering an issue with stack space during compilation?
