https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110495
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110495
--- Comment #4 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:f703d2fd3f03890a180e8cc04df087c208999e81
commit r14-2282-gf703d2fd3f03890a180e8cc04df087c208999e81
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110495
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110495
--- Comment #3 from Richard Biener ---
OK, that's a reasonable stance give we have VL vectors. I'll note that
previously build_vector looked like the following, so TREE_OVERFLOW was
set according to the encoded elements. Now that's no longer t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110495
--- Comment #2 from rsandifo at gcc dot gnu.org
---
The point of the builder is that, if you know the pattern,
you don't need to supply every element value to the builder.
(And indeed you can't when the vector is variable length.)
So something
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110495
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org,