https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90458
--- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- > In general on x86 the compiler handles stack allocation (and probing when > stack clash protection is enabled). However, on Windows targets that stuff > is actually handled by calls to __chkstk_ms. > > One could easily argue that stack-clash-protection should be a NOP or > generate an error in a Windows environment. Right, Windows has been doing stack clash protection since day #1, like for example Tru64, so the option should just be a NOP on Windows.
