https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100494
--- Comment #9 from J.M. Eubank <john at thesnappy dot net> --- > I am unfamiliar with what mitigations/flags the compiler has for trying to > control this. It would certainly be possible to monitor the call depth and > cease at a certain point, but Im not sure what needs to be queried. Is this > information communicated by a target in some way? and checked against some > criteria for passes which may need to limit their consumption? +1, this would be nice? I'm running a build with -Wl,--stack=10485760 (10 MiB) to see if this alleviates the problem. However, I'm definitely curious to see how this might be handled for other actually constrained targets where that's not an option - do they simply recommend not to use -O2?
