https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88531
--- Comment #8 from Florian Schornbaum
---
They are definitely a good source to ask.
We'll try to get in contact with them and see if we can get help/insight.
Thanks for all your input so far!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88531
--- Comment #6 from Florian Schornbaum
---
Thanks Jakub. That's good information to have.
We would certainly be willing to help since this is something that we would
really like GCC to be able to handle.
Does it make sense for us, as developer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88531
--- Comment #4 from Florian Schornbaum
---
Hi Jakub, Richard,
I hope you both had a good start into 2019.
I'm still wondering if there are any plans to make arbitrary index data types
work with gather/scatter?
If there are no such plans at th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88531
--- Comment #3 from Florian Schornbaum
---
Thank you for your very quick replies!
I'm aware of 88464 (I think this is the recent work you are referring to?), but
this had no effect on the index data type issue I was describing.
Even if the gat
: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: florian.schornbaum at siemens dot com
Target Milestone: ---
Hi,
I realized that GCC fails to vectorize simple loops if there are indirect loads
(or stores) and the index used
