https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105175
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105175
--- Comment #5 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:b789c44c6463452900f7b1e6d2a0af6567534bfc
commit r12-8054-gb789c44c6463452900f7b1e6d2a0af6567534bfc
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105175
Richard Biener changed:
What|Removed |Added
CC||dmalcolm at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105175
--- Comment #3 from Richard Biener ---
So vectorizable_operation correctly says target_support_p == false and then
goes
on with
target_support_p = (optab_handler (optab, vec_mode)
!= CODE_FOR_nothing);
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105175
--- Comment #2 from Andreas Krebbel ---
I would expect the vectorizer to only generate vector modes which would fit
into word mode if no hardware vector support is available. E.g. for:
struct {
unsigned a, b, c, d;
} s;
foo() {
s.a &= 42;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105175
Richard Biener changed:
What|Removed |Added
Component|rtl-optimization|tree-optimization
Last reconfirmed|
