https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69920
--- Comment #2 from Martin Jambor <jamborm at gcc dot gnu.org> --- (In reply to H.J. Lu from comment #1) > It may be caused by r233626. What do you mean by "may be?" I have just double checked that if I apply the patch to r233489 and run the test, it passes here on my x86_64-linux. Anyway, once I move to a newer trunk (in a day or three), I'll check again by reverting the change... unless someone finds a different culprit in the meantime.
