https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90471
--- Comment #18 from Daniel Fruzynski <bugzi...@poradnik-webmastera.com> --- Unfortunately default Valgrind tool (memcheck) does not look for stack issues. It has separate tool (sgcheck) which does this. I will try to use it too and see if it will something. One more thing come to my mind. gcc should use stack limit of host, not of target. I saw crashes on both Cygwin and Linux hosts, which have stack size limits 2032 and 8192, respectively. If gcc uses default host stack size, this would mean that bug is somewhere else.
