https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110273
--- Comment #13 from Zeb Figura <zfigura at codeweavers dot com> --- (In reply to Sam James from comment #11) > (In reply to Jens-Hanno Schwalm from comment #10) > > Hi, i think we found a very-similar issue in darktable code, you might look > > at > > > > https://github.com/darktable-org/darktable/pull/15742 > > > > If you're hitting this on another target than i686-w64-mingw32, please file > a new bug. We can always mark it as a dupe if it turns out to be, although I > suspect it isn't here. FWIW, I think the relevant part of i686-w64-ming32 is actually just STACK_REALIGN_DEFAULT. I can reproduce the same lack of alignment with "-mstackrealign -mavx512 -O2" with i386-linux-gnu, whereas "-mstackrealign -mavx2 -O2" does align the stack. [-O2 is necessary here otherwise gcc will just use vmovdqu and not bother aligning the stack. No idea what the more targeted optimization is.] I'd assume this is a bug with -mstackrealign, but I also don't understand what the intended purpose of -mstackrealign is. How does it differ from -mincoming-stack-boundary=2 or -mpreferred-stack-boundary=2?
