https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
--- Comment #44 from Eric Botcazou ---
> Thank you, Dmitry, but that particular solution may not be possible for me.
> When I try compiling with -mstackrealign -mpreferred-stack-boundary=5
> -mincoming-stack-boundary=5 instead of forcing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
--- Comment #43 from Avraham Adler ---
Thank you, Dmitry, but that particular solution may not be possible for me.
When I try compiling with -mstackrealign -mpreferred-stack-boundary=5
-mincoming-stack-boundary=5 instead of forcing unaligned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
--- Comment #42 from Dmitry Kazakov ---
Hi, Avraham!
> Does it remain true that the only option to get around this bug without
> killing all AVX2 is to pass "-Wa,-muse-unaligned-vector-move" when compiling
> using GCC on Windows 64? Thank you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
--- Comment #41 from Avraham Adler ---
It has been a few years since the last comment. I recently got hit by this bug
for the first time in about a decade and a half of compiling R for Windows 64
using GCC 13.2.0 as packaged in Rtools44 [1].
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
Eric Botcazou changed:
What|Removed |Added
Assignee|ebotcazou at gcc dot gnu.org |unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
--- Comment #40 from H.J. Lu ---
(In reply to Eric Botcazou from comment #37)
> > If the Windows ABI doesn't align stack or not as much as gcc assumes, then a
> > fix would ensure only automatic vars on Windows are accessed always using
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
--- Comment #39 from Eric Botcazou ---
> If SEH is the problem, can alignment be accounted for in cases where SEH is
> not in use (if there are any such cases)? I'm thinking of -fno-exceptions,
> and dwarf (on x86) or setjump/longjump
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
--- Comment #38 from R Copley ---
(A patch to emit unaligned instructions should probably resolve bug 49001
instead of this one, 54412.)
Could dynamic alignment be achieved, not for automatic variables and function
parameters, but for registers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
--- Comment #37 from Eric Botcazou ---
> If the Windows ABI doesn't align stack or not as much as gcc assumes, then a
> fix would ensure only automatic vars on Windows are accessed always using
> unaligned vector instructions provided dynamic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
Stephen Kitt changed:
What|Removed |Added
CC||steve at sk2 dot org
--- Comment #35
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
--- Comment #34 from Eric Botcazou ---
> It's unfortunate that the best and most common advice for using avx2 with
> gcc/mingw is to use a patched compiler. Might it be possible to accept
> Debian's patch upstream?
Sure, but they need to submit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
Cory Fields changed:
What|Removed |Added
CC||lists at coryfields dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
Chinoune changed:
What|Removed |Added
CC||mehdi.chinoune at hotmail dot
com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
Dmitry Kazakov changed:
What|Removed |Added
CC||dimula73 at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
Mingye Wang changed:
What|Removed |Added
CC||arthur200126 at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
--- Comment #29 from Yichao Yu ---
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412#c25
GCC is fully capable of aligning the stack. It just seems that different part
of it disagrees on what the current stack alignment is and whether a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
John Platts changed:
What|Removed |Added
CC||john_platts at hotmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
--- Comment #27 from Dmitry Kazakov ---
As a workaround, one can either use __attribute__((always_inline)) for *all*
the functions accepting __m256 or pass *all* arguments by const-ref. Const-ref
arguments are passed correctly.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
--- Comment #26 from Dmitry Kazakov ---
Created attachment 46133
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46133=edit
Test source for unaligned pass-by-value crash
Test file for the comment above
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
Dmitry Kazakov changed:
What|Removed |Added
CC||dimula73 at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
--- Comment #24 from Yichao Yu ---
Oh, and the test case above was compiled with -O3 (and -g -Wall -Wextra).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
Yichao Yu changed:
What|Removed |Added
CC||yyc1992 at gmail dot com
--- Comment #23
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
--- Comment #22 from Royi ---
Hello,
Any progress on this on GCC 8.x?
We really want GCC + AVX on Windows.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
Liu Hao changed:
What|Removed |Added
CC||lh_mouse at 126 dot com
--- Comment #21 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
--- Comment #20 from Eric Botcazou ---
> This comment could be important:
>
> https://stackoverflow.com/questions/30928265/mingw64-is-incapable-of-32-byte-
> stack-alignment-required-for-avx-on-windows-
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412
--- Comment #19 from Royi ---
This comment could be important:
https://stackoverflow.com/questions/30928265/mingw64-is-incapable-of-32-byte-stack-alignment-required-for-avx-on-windows-x64?noredirect=1#comment86499640_30928265.
Hopefully you'll
27 matches
Mail list logo
