https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87358
--- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Lijian Zhang from comment #9) > Hi Andrew, > I only reproduced this issue with gcc-7.3.0, but not able to reproduce the > failure with gcc-8.2.0/gcc-8.1.0 FSF released GCC 7.3.0 does not have the issue. Only the Linaro (and in turn Ubuntu)'s version of GCC 7.3.0 has the bug. The code was not introduced until after GCC 7 was branched off and GCC 8 was the trunk. > But from your description, gcc-8.2.0 still have this issue, and this issue > is target to be fixed in gcc-8.3.0? Yes GCC 8.2.0 has one part of the fix is now included in 8.3.0; the other part (which is also hit for Linaro's GCC 7.3.0) was included a few weeks after the originally bug was introduced when GCC 8 was the trunk.
