* [Bug rtl-optimization/21141] excessive stack usage
2005-04-21 6:05 [Bug tree-optimization/21141] New: excessive stack usage vda at port dot imtp dot ilyichevsk dot odessa dot ua
@ 2005-04-21 6:08 ` pinskia at gcc dot gnu dot org
2005-04-21 6:09 ` vda at port dot imtp dot ilyichevsk dot odessa dot ua
` (6 subsequent siblings)
7 siblings, 0 replies; 13+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-04-21 6:08 UTC (permalink / raw)
To: gcc-bugs
--
What |Removed |Added
----------------------------------------------------------------------------
Component|tree-optimization |rtl-optimization
Keywords| |missed-optimization, ra
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21141
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug rtl-optimization/21141] excessive stack usage
2005-04-21 6:05 [Bug tree-optimization/21141] New: excessive stack usage vda at port dot imtp dot ilyichevsk dot odessa dot ua
2005-04-21 6:08 ` [Bug rtl-optimization/21141] " pinskia at gcc dot gnu dot org
@ 2005-04-21 6:09 ` vda at port dot imtp dot ilyichevsk dot odessa dot ua
2005-04-21 6:18 ` [Bug rtl-optimization/21141] [3.4 Regression] " pinskia at gcc dot gnu dot org
` (5 subsequent siblings)
7 siblings, 0 replies; 13+ messages in thread
From: vda at port dot imtp dot ilyichevsk dot odessa dot ua @ 2005-04-21 6:09 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From vda at port dot imtp dot ilyichevsk dot odessa dot ua 2005-04-21 06:08 -------
Created an attachment (id=8695)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8695&action=view)
testcase
Use gcc -O2 -S t.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21141
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug rtl-optimization/21141] [3.4 Regression] excessive stack usage
2005-04-21 6:05 [Bug tree-optimization/21141] New: excessive stack usage vda at port dot imtp dot ilyichevsk dot odessa dot ua
2005-04-21 6:08 ` [Bug rtl-optimization/21141] " pinskia at gcc dot gnu dot org
2005-04-21 6:09 ` vda at port dot imtp dot ilyichevsk dot odessa dot ua
@ 2005-04-21 6:18 ` pinskia at gcc dot gnu dot org
2005-04-21 6:27 ` pinskia at gcc dot gnu dot org
` (4 subsequent siblings)
7 siblings, 0 replies; 13+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-04-21 6:18 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-21 06:18 -------
4.1.0/4.0.0 gives:
subl $268, %esp
which is better than 3.4.x.
3.4.0 gives:
subl $732, %esp
Only a 3.4 regression, confirmed:
subl $3516, %esp
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Keywords|ra |
Last reconfirmed|0000-00-00 00:00:00 |2005-04-21 06:18:37
date| |
Summary|excessive stack usage |[3.4 Regression] excessive
| |stack usage
Target Milestone|--- |3.4.4
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21141
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug rtl-optimization/21141] [3.4 Regression] excessive stack usage
2005-04-21 6:05 [Bug tree-optimization/21141] New: excessive stack usage vda at port dot imtp dot ilyichevsk dot odessa dot ua
` (2 preceding siblings ...)
2005-04-21 6:18 ` [Bug rtl-optimization/21141] [3.4 Regression] " pinskia at gcc dot gnu dot org
@ 2005-04-21 6:27 ` pinskia at gcc dot gnu dot org
2005-04-21 6:33 ` pinskia at gcc dot gnu dot org
` (3 subsequent siblings)
7 siblings, 0 replies; 13+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-04-21 6:27 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-21 06:27 -------
Note your testcase has uninitialized variables, well the arrays are uninitizalized, after fixing them, it
gets worse:
subl $3532, %esp
Though on 4.0.0/4.1.0, we get better:
subl $260, %esp
which is funny but what ever.
3.3.3 by the way gives:
subl $636, %esp
3.4.0 gives:
subl $748, %esp
3.2.3:
subl $444, %esp
3.0.4:
subl $556, %esp
2.95.3:
subl $508,%esp
so 4.0.0/4.1.0 gices the best results.
--
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |3.4.4
Known to work| |3.3.3 3.4.0 4.0.0 4.1.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21141
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug rtl-optimization/21141] [3.4 Regression] excessive stack usage
2005-04-21 6:05 [Bug tree-optimization/21141] New: excessive stack usage vda at port dot imtp dot ilyichevsk dot odessa dot ua
` (3 preceding siblings ...)
2005-04-21 6:27 ` pinskia at gcc dot gnu dot org
@ 2005-04-21 6:33 ` pinskia at gcc dot gnu dot org
2005-04-21 11:29 ` vda at port dot imtp dot ilyichevsk dot odessa dot ua
` (2 subsequent siblings)
7 siblings, 0 replies; 13+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-04-21 6:33 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-21 06:33 -------
Hmm, with -fomit-frame-pointer, the stack usage goes back to an okay value:
subl $604, %esp
I think this is just another case where spills are no not reused, see PR 17838. so -fomit-frame-pointer
causes the spilling to go down. 4.0.0 reduces the stack usage by making the arrays really each 8
variables.
--
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO| |17838
nThis| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21141
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug rtl-optimization/21141] [3.4 Regression] excessive stack usage
2005-04-21 6:05 [Bug tree-optimization/21141] New: excessive stack usage vda at port dot imtp dot ilyichevsk dot odessa dot ua
` (4 preceding siblings ...)
2005-04-21 6:33 ` pinskia at gcc dot gnu dot org
@ 2005-04-21 11:29 ` vda at port dot imtp dot ilyichevsk dot odessa dot ua
2005-04-21 11:29 ` vda at port dot imtp dot ilyichevsk dot odessa dot ua
2005-05-19 17:43 ` mmitchel at gcc dot gnu dot org
7 siblings, 0 replies; 13+ messages in thread
From: vda at port dot imtp dot ilyichevsk dot odessa dot ua @ 2005-04-21 11:29 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From vda at port dot imtp dot ilyichevsk dot odessa dot ua 2005-04-21 11:27 -------
>Though on 4.0.0/4.1.0, we get better:
> subl $260, %esp
It's way too good. Declared locals should take 512 bytes, plus
any temporaries for spills.
Please find fixed testcase. My fault.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21141
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug rtl-optimization/21141] [3.4 Regression] excessive stack usage
2005-04-21 6:05 [Bug tree-optimization/21141] New: excessive stack usage vda at port dot imtp dot ilyichevsk dot odessa dot ua
` (5 preceding siblings ...)
2005-04-21 11:29 ` vda at port dot imtp dot ilyichevsk dot odessa dot ua
@ 2005-04-21 11:29 ` vda at port dot imtp dot ilyichevsk dot odessa dot ua
2005-05-19 17:43 ` mmitchel at gcc dot gnu dot org
7 siblings, 0 replies; 13+ messages in thread
From: vda at port dot imtp dot ilyichevsk dot odessa dot ua @ 2005-04-21 11:29 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From vda at port dot imtp dot ilyichevsk dot odessa dot ua 2005-04-21 11:29 -------
Whoops.... no, locals are 256 bytes only.
(/me is looking for some coffee)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21141
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug rtl-optimization/21141] [3.4 Regression] excessive stack usage
2005-04-21 6:05 [Bug tree-optimization/21141] New: excessive stack usage vda at port dot imtp dot ilyichevsk dot odessa dot ua
` (6 preceding siblings ...)
2005-04-21 11:29 ` vda at port dot imtp dot ilyichevsk dot odessa dot ua
@ 2005-05-19 17:43 ` mmitchel at gcc dot gnu dot org
7 siblings, 0 replies; 13+ messages in thread
From: mmitchel at gcc dot gnu dot org @ 2005-05-19 17:43 UTC (permalink / raw)
To: gcc-bugs
--
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|3.4.4 |3.4.5
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21141
^ permalink raw reply [flat|nested] 13+ messages in thread