[Bug target/102404] Loop vectorized with 32 byte vectors actually uses 16 byte vectors

2021-09-21 Thread crazylht at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102404 --- Comment #6 from Hongtao.liu --- (In reply to Hongtao.liu from comment #5) > (In reply to Freddie Witherden from comment #4) > > Created attachment 51485 [details] > > Clang assembly. > > It seems to be because the current GCC loop vectorize

[Bug target/102404] Loop vectorized with 32 byte vectors actually uses 16 byte vectors

2021-09-21 Thread crazylht at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102404 --- Comment #5 from Hongtao.liu --- (In reply to Freddie Witherden from comment #4) > Created attachment 51485 [details] > Clang assembly. It seems to be because the current GCC loop vectorizer does not support different vector sizes, and here

[Bug target/102404] Loop vectorized with 32 byte vectors actually uses 16 byte vectors

2021-09-20 Thread freddie at witherden dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102404 --- Comment #4 from Freddie Witherden --- Created attachment 51485 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51485&action=edit Clang assembly.

[Bug target/102404] Loop vectorized with 32 byte vectors actually uses 16 byte vectors

2021-09-20 Thread freddie at witherden dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102404 --- Comment #3 from Freddie Witherden --- (In reply to Richard Biener from comment #2) > 32 bytes are 256 bits (ymm), 64 bytes are 512 bits (zmm). GCC does not > consider zmm vectorization because > > t.c:25:37: missed: loop does not have eno

[Bug target/102404] Loop vectorized with 32 byte vectors actually uses 16 byte vectors

2021-09-20 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102404 Richard Biener changed: What|Removed |Added Target|x86_64 |x86_64-*-* Status|UNCONFIR