--- Comment #10 from steven at gcc dot gnu dot org 2005-11-05 10:48 ---
This doesn't fail for me with the test case from comment #6... :-(
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23453
--- Comment #9 from mmitchel at gcc dot gnu dot org 2005-10-31 05:09
---
Leaving as P2.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23453
--- Comment #8 from bonzini at gcc dot gnu dot org 2005-10-14 11:38 ---
> gcse after reload may move loads from stack around stack pointer changes. here
> is simple workaround, it is supposed to prevent gcse after reload from
> touching
> expressions containing stack pointer at all.
Of
--
What|Removed |Added
Target Milestone|4.0.2 |4.0.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23453
--- Additional Comments From belyshev at depni dot sinp dot msu dot ru
2005-08-19 19:51 ---
gcse after reload may move loads from stack around stack pointer changes. here
is simple workaround, it is supposed to prevent gcse after reload from touching
expressions containing stack pointer
--- Additional Comments From belyshev at depni dot sinp dot msu dot ru
2005-08-19 01:03 ---
Single-file testcase, compile with "-march=i486 -O2 -fomit-frame-pointer
-fno-strict-aliasing -fgcse-after-reload":
bar ()
{
exit (0);
}
baz (x)
{
return x;
}
foo ()
{
abort ();
}
ker0 (
