https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30271
--- Comment #14 from GCC Commits ---
The master branch has been updated by Jiu Fu Guo :
https://gcc.gnu.org/g:4759383245ac97a5c83c0272f0a831f2a26ea5c1
commit r14-6674-g4759383245ac97a5c83c0272f0a831f2a26ea5c1
Author: Jiufu Guo
Date: Tue Dec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30271
Jiu Fu Guo changed:
What|Removed |Added
CC||guojiufu at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30271
luoxhu at gcc dot gnu.org changed:
What|Removed |Added
CC||luoxhu at gcc dot gnu.org
--- Comment #11 from pinskia at gcc dot gnu dot org 2008-12-29 23:51
---
(In reply to comment #10)
Hmm, this patch bootstraps just fine on the 4.3 branch but causes miscompares
on the trunk (the 4.3 branch had checking on also when I bootstrapped it on
i386-darwin8.11).
--
--- Comment #9 from zadeck at naturalbridge dot com 2008-12-15 15:32
---
Andrew,
What is your point here?
1) Is it your claim that anything that is arg_pointer_rtx related would
automatically qualify as being safe enough to remove dead stores to?
or
2) Is it your claim that if we
--- Comment #10 from pinskia at gcc dot gnu dot org 2008-12-16 02:08
---
(In reply to comment #9)
Andrew,
What is your point here?
My point here is that currently we do:
gi-frame_related =
(base == frame_pointer_rtx) || (base == hard_frame_pointer_rtx);
But if we
--- Comment #8 from pinskia at gcc dot gnu dot org 2008-12-11 04:42 ---
So the problem with the stores here is that the base is arg_pointer_rtx which
is still a frame pointer related offset. I think the same can be said is true
of stack_pointer_rtx too. We only set frame_related for
