[Bug tree-optimization/68640] foo restrict propagated to foo._omp_fn.0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68640 vries at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--

[Bug tree-optimization/68640] foo restrict propagated to foo._omp_fn.0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68640 --- Comment #9 from vries at gcc dot gnu.org --- Author: vries Date: Tue Dec 8 14:17:42 2015 New Revision: 231411 URL: https://gcc.gnu.org/viewcvs?rev=231411&root=gcc&view=rev Log: Clear restrict in install_var_field 2015-12-08 Tom de Vries

[Bug tree-optimization/68640] foo restrict propagated to foo._omp_fn.0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68640 vries at gcc dot gnu.org changed: What|Removed |Added Keywords||patch Assignee|unass

[Bug tree-optimization/68640] foo restrict propagated to foo._omp_fn.0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68640 --- Comment #7 from vries at gcc dot gnu.org --- Filed related PR68768 - '[fortran] propagate foo restrict to foo._omp_fn.0', where AFAIU keeping the restrict is legal for fortran with -fno-cray-pointers.

[Bug tree-optimization/68640] foo restrict propagated to foo._omp_fn.0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68640 --- Comment #6 from vries at gcc dot gnu.org --- > The definition of restrict allows for new temporaries. If you do "q = p + > 1;", then thereafter q is based on p. (If you do assignments between > restricted pointer objects, you also need to

[Bug tree-optimization/68640] foo restrict propagated to foo._omp_fn.0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68640 --- Comment #5 from joseph at codesourcery dot com --- The definition of restrict allows for new temporaries. If you do "q = p + 1;", then thereafter q is based on p. (If you do assignments between restricted pointer objects, you also need to

[Bug tree-optimization/68640] foo restrict propagated to foo._omp_fn.0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68640 Marc Glisse changed: What|Removed |Added CC||joseph at codesourcery dot com --- Comment

[Bug tree-optimization/68640] foo restrict propagated to foo._omp_fn.0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68640 vries at gcc dot gnu.org changed: What|Removed |Added CC||glisse at gcc dot gnu.org ---

[Bug tree-optimization/68640] foo restrict propagated to foo._omp_fn.0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68640 --- Comment #2 from vries at gcc dot gnu.org --- (In reply to Richard Biener from comment #1) > Is it used because it ends up in the static chain of the omp_fn and uses the > same (original) qualifiers? And the static chain itself is passed "by >

[Bug tree-optimization/68640] foo restrict propagated to foo._omp_fn.0

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68640 --- Comment #1 from Richard Biener --- Is it used because it ends up in the static chain of the omp_fn and uses the same (original) qualifiers? And the static chain itself is passed "by reference" and thus gets its fields looked at and restrict