https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67226
--- Comment #2 from Mikael Pettersson <mikpelinux at gmail dot com> --- This bug is clearly related to PR65358. This PR's test case is NOT fixed by the final fix for PR65358 (r223753), but it IS fixed (on both trunk and gcc-5 branch) by the initial proposed fix for PR65358: https://gcc.gnu.org/ml/gcc-patches/2015-03/msg01014.html Thus it seems that the changes made to that fix between the initial submission and the final commit broke it.
