[Bug tree-optimization/109806] 13.1.0 cc1plus stack smashing crash with C array of complex structs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806 --- Comment #6 from Andrew Pinski --- Reducing (I can get the fault if we reduce the stack limit down to 1024 on Linux via `ulimit -s 1024` ).
[Bug tree-optimization/109806] 13.1.0 cc1plus stack smashing crash with C array of complex structs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806 --- Comment #5 from Richard Biener --- (In reply to Amyspark from comment #4) > (In reply to Richard Biener from comment #2) > > Likely a duplicate of a bug where ranger runs out of stack on windows > > targets. > > I think you mean bug 109695? If so, it affects GCC 13 as well. Yeah, the rev in that bug increases stack requirement even more though, but yes, I think the problem is the same in principle.
[Bug tree-optimization/109806] 13.1.0 cc1plus stack smashing crash with C array of complex structs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806 --- Comment #4 from Amyspark --- (In reply to Richard Biener from comment #2) > Likely a duplicate of a bug where ranger runs out of stack on windows > targets. I think you mean bug 109695? If so, it affects GCC 13 as well.
[Bug tree-optimization/109806] 13.1.0 cc1plus stack smashing crash with C array of complex structs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806 --- Comment #3 from Amyspark --- Created attachment 55046 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55046=edit ZIP copy of the Github gist
[Bug tree-optimization/109806] 13.1.0 cc1plus stack smashing crash with C array of complex structs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806 Richard Biener changed: What|Removed |Added CC||amacleod at redhat dot com --- Comment #2 from Richard Biener --- Likely a duplicate of a bug where ranger runs out of stack on windows targets.
[Bug tree-optimization/109806] 13.1.0 cc1plus stack smashing crash with C array of complex structs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109806 --- Comment #1 from Andrew Pinski --- >it's 1.6MB, so it was impossible to attach them here uncompressed Can you try to compress it and attach it?