https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92865
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92865
--- Comment #1 from Hongtao.liu ---
I'll take a look.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92865
Martin Liška changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92865
--- Comment #3 from Hongtao.liu ---
Since TARGET_XOP only supports 128-bit vector compare, ix86_valid_mask_cmp_mode
should also handle 256/512-bit vector compare when avx512f is avalable.
untested patch
@@ -3428,7 +3428,7 @@ static bool
ix86_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92865
--- Comment #4 from Richard Biener ---
(In reply to Hongtao.liu from comment #3)
> Since TARGET_XOP only supports 128-bit vector compare,
> ix86_valid_mask_cmp_mode should also handle 256/512-bit vector compare when
> avx512f is avalable.
>
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92865
--- Comment #5 from Hongtao.liu ---
(In reply to Richard Biener from comment #4)
> (In reply to Hongtao.liu from comment #3)
> > Since TARGET_XOP only supports 128-bit vector compare,
> > ix86_valid_mask_cmp_mode should also handle 256/512-bit ve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92865
--- Comment #6 from Hongtao.liu ---
The missing point of my patch is for 512-bit vector compare, integer mask
vector compare still should be used even with target_xop, that's the root cause
of this issue.
Refer to this part.
---
- i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92865
--- Comment #7 from liuhongt at gcc dot gnu.org ---
Author: liuhongt
Date: Wed Dec 11 08:06:06 2019
New Revision: 279214
URL: https://gcc.gnu.org/viewcvs?rev=279214&root=gcc&view=rev
Log:
Fix unrecognizable insn of pr92865.
gcc/
PR target/92
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92865
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC|
