https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60997
Richard Biener changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60997
--- Comment #6 from Jakub Jelinek ---
Also, the compiler really isn't allowed to interchange the !$OMP DO loop
(outermost) with the inner ones, it has different semantics because of the
markup. The compiler could still interchange the inner two
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60997
--- Comment #5 from Jakub Jelinek ---
That is not possible.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60997
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60997
--- Comment #3 from Mircea Namolaru ---
It is not that -floop-interchange is disabled, but the code received by
graphite is different if the option -fopenmp is enabled. In this case the check
for data
dependencies required by loop-interchange fail
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60997
--- Comment #2 from Dominique d'Humieres ---
> IIRC -fopenmp has similar issues for vectorization (it defeats
> points-to analysis)
PR46032?
[Book15] f90/bug% g++ -Ofast pr46032.cpp -fopt-info-vec -fgraphite
-fgraphite-identity -floop-block -flo
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60997
--- Comment #1 from Richard Biener ---
IIRC -fopenmp has similar issues for vectorization (it defeats points-to
analysis)
