[Bug tree-optimization/49367] missed optimization with __restrict field

2015-09-29 Thread vries at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49367 vries at gcc dot gnu.org changed: What|Removed |Added CC||vries at gcc dot gnu.org --- C

[Bug tree-optimization/49367] missed optimization with __restrict field

2011-06-14 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49367 --- Comment #3 from Richard Guenther 2011-06-14 12:44:35 UTC --- The last example is because with a restrict qualified loaded pointer the later conversion to a restrict qualified pointer is thrown away. As for the first example the only case tha

[Bug tree-optimization/49367] missed optimization with __restrict field

2011-06-13 Thread jason at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49367 --- Comment #2 from Jason Merrill 2011-06-13 18:11:04 UTC --- (In reply to comment #1) > As a1 and a2 are not restrict qualified they may point to the same object > and thus the "two" restrict pointers are based on each other. Marking them with

[Bug tree-optimization/49367] missed optimization with __restrict field

2011-06-12 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49367 Richard Guenther changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|