--- Comment #7 from steven at gcc dot gnu dot org 2009-06-30 08:21 ---
Please adjust the test case:
/* { dg-options "-O2 -Os -fdump-tree-sink-stats" } */
This makes no sense, -Os implies -O2. So it should be:
/* { dg-options "-Os -fdump-tree-sink-stats" } */
--
http://gcc.gnu.or
--
steven at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.5.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40416
--- Comment #6 from carrot at google dot com 2009-06-30 07:42 ---
http://gcc.gnu.org/ml/gcc-cvs/2009-06/msg01067.html
--
carrot at google dot com changed:
What|Removed |Added
-
--- Comment #5 from steven at gcc dot gnu dot org 2009-06-22 16:32 ---
Did that patch go in already?
--
steven at gcc dot gnu dot org changed:
What|Removed |Added
--
ramana at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfir
--- Comment #4 from carrot at google dot com 2009-06-15 02:32 ---
In the source code, only two extra variables next_runs and next_alpha need to
be preserved through the while loop.
But in the gcc generated code, three variables are kept through the first loop.
They are next_alpha, origi
--- Comment #3 from carrot at google dot com 2009-06-15 02:26 ---
Created an attachment (id=17998)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17998&action=view)
preprocessed test case
A possible code sequence without spilling is:
push{r4, r5, r6, r7, lr}
ad
--- Comment #2 from ramana at gcc dot gnu dot org 2009-06-12 12:54 ---
(In reply to comment #1)
> Created an attachment (id=17983)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17983&action=view) [edit]
> test case
>
Your attachment didn't have #include - Please try and supply
p
--- Comment #1 from carrot at google dot com 2009-06-11 14:34 ---
Created an attachment (id=17983)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17983&action=view)
test case
The spilling is occurred around the first loop:
push{r4, r5, r6, r7, lr}
sub sp, s
