[Bug middle-end/82898] Aliasing knowledge is not used to replace memmove with memcpy

2020-03-20 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82898 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED See Also|

[Bug middle-end/82898] Aliasing knowledge is not used to replace memmove with memcpy

2017-11-08 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82898 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org --- Comment #5

[Bug middle-end/82898] Aliasing knowledge is not used to replace memmove with memcpy

2017-11-08 Thread rguenther at suse dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82898 --- Comment #4 from rguenther at suse dot de --- On Wed, 8 Nov 2017, antoshkka at gmail dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82898 > > --- Comment #3 from Antony Polukhin --- > > At least in the gcc model, the type of

[Bug middle-end/82898] Aliasing knowledge is not used to replace memmove with memcpy

2017-11-08 Thread antoshkka at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82898 --- Comment #3 from Antony Polukhin --- > At least in the gcc model, the type of a pointer is meaningless > as long as you do not dereference it using that type<...> OK, does dereferencing the pointers change anything? void foo(int* i, const

[Bug middle-end/82898] Aliasing knowledge is not used to replace memmove with memcpy

2017-11-08 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82898 Richard Biener changed: What|Removed |Added Keywords||alias, missed-optimization

[Bug middle-end/82898] Aliasing knowledge is not used to replace memmove with memcpy

2017-11-08 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82898 --- Comment #1 from Marc Glisse --- At least in the gcc model, the type of a pointer is meaningless as long as you do not dereference it using that type, so I am not sure what can be done here.