https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100494
--- Comment #7 from J.M. Eubank <john at thesnappy dot net> --- Created attachment 51024 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51024&action=edit sha1.c.038t.evrp.gz > Does the compilation not finish? or just take ma very long time? On the > other targets it finishes very quickly, spending very little time in EVRP. > Its unclear to me why this target would be so different, unless a deep call > stack is a problem. The default stack limit is 1 MiB, so a bit of quick math from the above addresses I posted puts us at 1.2 MiB - this definitely is in line with chkstk failing as we go out of bounds, I think. > Does the issue go away with --param=evrp-mode=legacy ? Yes, it does! > If it does seem to go into an infinite loop, can you try it with > -fdump-tree-evrp-details --param=evrp-mode=trace Attached. joeub@DESKTOP-1LUONFR MINGW64 /crossdev/gccmaster/build-cross4/binutils/libiberty $ /crossdev/gccmaster/host-toolchain-cross4/bin/x86_64-w64-mingw32-gcc -I . -I C:/crossdev/src/binutils-git-2_36_1/libiberty/../include -iprefix c:\crossdev\gccmaster\host-toolchain-cross4\bin\../lib/gcc/x86_64-w64-mingw32/11.1.0/ -D_REENTRANT -D HAVE_CONFIG_H -D __USE_MINGW_ACCESS -D _GNU_SOURCE C:/crossdev/src/binutils-git-2_36_1/libiberty/sha1.c -g -O2 -c -fdump-tree-evrp-details --param=evrp-mode=trace joeub@DESKTOP-1LUONFR MINGW64 /crossdev/gccmaster/build-cross4/binutils/libiberty $ echo $? 1 <-- indicator for chkstk failure in cc1 joeub@DESKTOP-1LUONFR MINGW64 /crossdev/gccmaster/build-cross4/binutils/libiberty $ gzip sha1.c.038t.evrp
