[Bug target/54412] minimal 32-byte stack alignment with -mavx on 64-bit Windows

2019-04-10 Thread dimula73 at gmail 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

[Bug target/54412] minimal 32-byte stack alignment with -mavx on 64-bit Windows

2019-04-10 Thread dimula73 at gmail dot com
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&action=edit Test source for unaligned pass-by-value crash Test file for the comment above

[Bug target/54412] minimal 32-byte stack alignment with -mavx on 64-bit Windows

2019-04-10 Thread dimula73 at gmail 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.

[Bug target/54412] minimal 32-byte stack alignment with -mavx on 64-bit Windows

2021-08-24 Thread dimula73 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412 Dmitry Kazakov changed: What|Removed |Added CC||dimula73 at gmail dot com --- Comment

[Bug target/54412] minimal 32-byte stack alignment with -mavx on 64-bit Windows

2024-03-27 Thread dimula73 at gmail dot com via Gcc-bugs
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