http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60086
--- Comment #5 from Andrey Belevantsev abel at gcc dot gnu.org ---
(In reply to Jakub Jelinek from comment #1)
...
doesn't reorder those is that RA allocates the same register. With -O3
-mavx -fselective-scheduling2 the stores are also
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60086
--- Comment #6 from Andrey Belevantsev abel at gcc dot gnu.org ---
Forgot to mention that we end up scheduling this block in 21 cycles while the
regular scheduling needs 24. Not that it's so important though.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60086
Alexander Monakov amonakov at gcc dot gnu.org changed:
What|Removed |Added
CC||amonakov
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60086
--- Comment #8 from Marcin Krotkiewski marcin.krotkiewski at gmail dot com ---
(In reply to Andrey Belevantsev from comment #5)
At this point insn 461 is dead but we do not notice, and it doesn't look
easy. I think there was some suggestion in
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60086
--- Comment #9 from Alexander Monakov amonakov at gcc dot gnu.org ---
By good code I was referring to the fact that your 4.7 asm does not contain
stack (%rbp) references in the vectorized loop.
Historically, first scheduling (-fschedule-insns)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60086
Jakub Jelinek jakub at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60086
--- Comment #2 from Marcin Krotkiewski marcin.krotkiewski at gmail dot com ---
Jakub, thank you for your comments.
GCC right now only handles __restrict on function parameters, so in this
case the aliasing info isn't known. While the loop is
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60086
Marek Polacek mpolacek at gcc dot gnu.org changed:
What|Removed |Added
CC||mpolacek at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60086
--- Comment #4 from Richard Biener rguenth at gcc dot gnu.org ---
As of posix_memalign the issue is not so much that of alias analysis (we could
handle it but we don't have a builtin right now) but that of alignment analysis
which doesn't
