https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111889
Haochen Jiang changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111889
--- Comment #6 from CVS Commits ---
The master branch has been updated by Haochen Jiang :
https://gcc.gnu.org/g:fd5147177b9fa04943a3a55512b81f8f46ab4ac5
commit r14-5140-gfd5147177b9fa04943a3a55512b81f8f46ab4ac5
Author: Haochen Jiang
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111889
--- Comment #5 from Haochen Jiang ---
It is actually a legacy issue from this:
$ cat 2.c
#include
__attribute__ ((target ("no-avx2")))
void foo ()
{
return _mm_empty ();
}
$ x86_64-pc-linux-gnu-gcc -O2 -mavx512f 2.c
It will also fail.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111889
Hongtao.liu changed:
What|Removed |Added
CC||crazylht at gmail dot com
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111889
Richard Biener changed:
What|Removed |Added
Target||x86_64-*-*
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111889
--- Comment #3 from Haochen Jiang ---
My proposal for this problem is to also push "no-evex512" when defining 128/256
intrins. But I am not sure if there will be some potential problems.
Currently working on an experiment on that.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111889
--- Comment #2 from Haochen Jiang ---
Here is the Godbolt example of that:
https://godbolt.org/z/b3n8h4rb1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111889
--- Comment #1 from Haochen Jiang ---
(In reply to Haochen Jiang from comment #0)
> Created attachment 56155 [details]
> Simple testcase
>
> With this simple testcase and command like this:
>
> x86_64-pc-linux-gnu-gcc -O2 -march=x86-64 1.c
>
