[Bug tree-optimization/30187] accessing an element via a "pointer" on a vector does not cause vec_extract to be used (non constant index)

2020-01-22 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30187 Andrew Pinski changed: What|Removed |Added Status|NEW |UNCONFIRMED Ever confirmed|1

[Bug tree-optimization/30187] accessing an element via a "pointer" on a vector does not cause vec_extract to be used (non constant index)

2020-01-22 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30187 --- Comment #3 from Andrew Pinski --- Here is the interesting thing: #define vector __attribute__((vector_size(16))) float f(vector float t, int i) { vector int tt = {i, i, i, i}; vector float r = __builtin_shuffle(t, tt); return r[0]; } -

[Bug tree-optimization/30187] accessing an element via a "pointer" on a vector does not cause vec_extract to be used (non constant index)

2016-08-27 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30187 --- Comment #2 from Andrew Pinski --- I wonder if we could use a __builtin_shuffle here followed by an extraction.

[Bug tree-optimization/30187] accessing an element via a "pointer" on a vector does not cause vec_extract to be used (non constant index)

2009-04-22 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2009-04-22 21:56 --- Confirmed. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCON

[Bug tree-optimization/30187] accessing an element via a "pointer" on a vector does not cause vec_extract to be used (non constant index)

2006-12-12 Thread pinskia at gcc dot gnu dot org
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Severity|normal |enhancement http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30187