http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38621
Oleg Endo <olegendo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
--- Comment #13 from Oleg Endo <olegendo at gcc dot gnu.org> 2012-07-18
18:57:38 UTC ---
(In reply to comment #11)
> (In reply to comment #10)
> > I've tried to reproduce the issue with rev 189549 (GCC 4.8),
> > GCC 4.7.2 20120711 (prerelease) and GCC 4.6.4 20120716 (prerelease).
> > It seems this is no longer an issue.
>
> 4.6 and 4.7 are failing with -fschedule-insns for me. We changed
> the default behavior so that -fno-schedule-insns is default.
> 4.8 doesn't fail even with -fschedule-insns. I guess that your
> patches for index addressing fix it on trunk. Perhaps we can
> close this PR because it's fixed on trunk and looks no hope to fix
> it for 4.6 and 4.7 compilers with -fschedule-insns.
OK. I think it's better to take any -fschedule-insns follow ups to PR 22553.
