--- Comment #3 from rakdver at gcc dot gnu dot org 2009-04-25 22:44 ---
I cannot reproduce this in 4.5; all the unnecessary loads are removed.
The fix is to avoid the load part of load-store-motion of course.
I've considered this, but it seems much easier to just let the unnecessary
--
jakub at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|4.4.0 |4.4.1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39612
--
jakub at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39612
--
rakdver at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|unassigned at gcc dot gnu |rakdver at gcc dot gnu dot
|dot org
--- Comment #2 from rguenth at gcc dot gnu dot org 2009-04-02 09:43 ---
Confirmed. store motion transforms a loop
for (;;)
a[0] = 1;
to
lsmtmp = a[0];
for (;;)
lsmtmp = 1;
a[0] = lsmtmp;
introducing a load from uninitialized memory. We don't seem to DCE/DSE this
for the
