[Bug tree-optimization/89617] memmove used even after runtime guard against overlap

2019-03-07 Thread jzwinck at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89617 --- Comment #2 from John Zwinck --- Jakub, here is a similar example using structs instead of arrays. It still generates different code, with RESTRICT giving memcpy instead of mov, but no RESTRICT still using memmove which is suboptimal. st

[Bug tree-optimization/89617] memmove used even after runtime guard against overlap

2019-03-07 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89617 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #1

[Bug tree-optimization/89617] memmove used even after runtime guard against overlap

2019-03-06 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89617 Andrew Pinski changed: What|Removed |Added Keywords||missed-optimization Component|c