https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63679
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
--- Comment #25 from Richard Biener <rguenth at gcc dot gnu.org> ---
No, aarch64 still commits the initializer to memory so the patch doesn't help
it for the testcase in the end. It still improves things a bit.
I'm quite sure we can't fix this in a target independent way for GCC 5, thus
the only chance is to make aarch64 not commit the initializer to memory.
That is also the real regression (aarch64 changed to commit the initializer
to memory).
aarch64 is secondary target only thus this missed-optimization shouldn't block
the release.
