https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66675
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed|2015-06-25 00:00:00 |2021-8-19
--- Comment #6 from Andrew Pin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66675
Andrew Pinski changed:
What|Removed |Added
Target|aarch64*-*-*, arm*-*-* |
--- Comment #5 from Andrew Pinski ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66675
--- Comment #4 from Andrew Pinski ---
Note for this optimization to be useful there needs to be a heurstic to find
out if folding CONSTRUCTOR + VECTOR_CST is going to be only one or no other
add. Or using one element of the whole vector.
AKA it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66675
--- Comment #3 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #2)
> Basically VECTOR_CST + VECTOR_CST is not optimized at all. I bet almost all
> operations that act on VECTOR_CST are not optimized including and not
> limited to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66675
--- Comment #2 from Andrew Pinski ---
Basically VECTOR_CST + VECTOR_CST is not optimized at all. I bet almost all
operations that act on VECTOR_CST are not optimized including and not limited
to PLUS, SUB, MULTIPLY, DIVIDE, SHIFT, IOR, XOR, and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66675
--- Comment #1 from Ramana Radhakrishnan ---
The GCC vector speak variant is as below.
typedef char v8qi __attribute__ ((vector_size (8)));
int main(int argc, char *argv[])
{
v8qi a = {argc, 1, 2, 3, 4, 5, 6, 7};
v8qi b = {0, 1, 2, 3, 4,
