http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57422
Andrey Belevantsev <abel at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Andrey Belevantsev <abel at gcc dot gnu.org> ---
See the thread in gcc-patches: the test does not make sense as it is very
sensitive on the scheduler decisions -- even now I had to use the exact
reported revision to get the failure. I have added extra asserts in the
separate commit instead.
