http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52491
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-03-05
Ever Confirmed|0 |1
--- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-03-05
13:34:31 UTC ---
Confirmed.
I think the ppc movmisalign optabs are bogus, they do not implement
movmisalign but a re-aligned load/store contrary to its documentation:
@cindex @code{movmisalign@var{m}} instruction pattern
@item @samp{movmisalign@var{m}}
This variant of a move pattern is designed to load or store a value
from a memory address that is not naturally aligned for its mode.
For a store, the memory will be in operand 0; for a load, the memory
will be in operand 1. The other operand is guaranteed not to be a
memory, so that it's easy to tell whether this is a load or store.
This pattern is used by the autovectorizer, and when expanding a
@code{MISALIGNED_INDIRECT_REF} expression.
(scratch the last sentence, there is no MISALIGNED_INDIRECT_REF anymore).
