>
> In http://gcc.gnu.org/ml/gcc/2006-06/msg00185.html, your wrote:
>
> > So, two questions: any idea why 4.1.1 is no longer able to
> > automatically inline memcpys and why is the source operand for
> > movmemsi not know to be as widely aligned as it actually is?
>
> See PR middle-end/27226
>
In http://gcc.gnu.org/ml/gcc/2006-06/msg00185.html, your wrote:
So, two questions: any idea why 4.1.1 is no longer able to automatically
inline memcpys and why is the source operand for movmemsi not know to be as
widely aligned as it actually is?
See PR middle-end/27226
Hi,
I'm updating a port from 3.4.6 to 4.1.1. In 3.4.6, I hadn't implemented
movmemsi patterns, but the compiler could still inline memcpy's (and also
strcpys where source string is a const) by itself. After updating to 4.1.1,
calls to memcpy are always generated.
I've had a bash at implementing
