https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70628
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pinskia at gcc dot gnu.org
Target Milestone|--- |5.4
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andreas Schwab from comment #2)
> a714a09ad18ee606064bbaac690ab1c8121dcc31 is the first bad commit
> commit a714a09ad18ee606064bbaac690ab1c8121dcc31
> Author: mkuvyrkov <mkuvyrkov@138bc75d-0d04-0410-961f-82ee72b054a4>
> Date: Fri Oct 24 08:22:12 2014 +0000
>
> git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@216620
> 138bc75d-0d04-0410-961f-82ee72b054a4
Since that is just a scheduler change, it exposes the latent bug. Now the
problem is most likely related to Pmode != ptrmode (this is correct here but
the var-tracking code does not do the correct thing).
