public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/16987] [3.5 Regression] Excessive stack allocation (totally unused)
Date: Wed, 11 Aug 2004 19:44:00 -0000	[thread overview]
Message-ID: <20040811194455.20618.qmail@sourceware.org> (raw)
In-Reply-To: <20040811181008.16987.giovannibajo@libero.it>


------- Additional Comments From giovannibajo at libero dot it  2004-08-11 19:44 -------
The stack allocation problem is present in GCC since at least GCC 3.2.2, and 
the tree optimizers didn't fix it.

2.95.3 allocated more stack space without the constructor but less stack space 
with the constructor:

-       subl $20,%esp
+       subl $36,%esp

So we now allocate 64 bytes instead of 36. I flag this as a regression, which 
is surely important for any kind of embedded targets.

The missed optimization which Andrew speaks about in comment #1 is a known 
problem already tracked elsewhere (as he said).

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to fail|                            |3.3.3 3.4.0 3.5.0
      Known to work|                            |2.95.3


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16987


  parent reply	other threads:[~2004-08-11 19:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 18:10 [Bug tree-optimization/16987] New: " giovannibajo at libero dot it
2004-08-11 18:19 ` [Bug tree-optimization/16987] [3.5 Regression] " pinskia at gcc dot gnu dot org
2004-08-11 18:21 ` pinskia at gcc dot gnu dot org
2004-08-11 19:44 ` giovannibajo at libero dot it [this message]
2004-08-11 19:45 ` [Bug tree-optimization/16987] [3.3/3.4/3.5 " giovannibajo at libero dot it
2004-08-29 18:25 ` mmitchel at gcc dot gnu dot org
2004-09-03 22:05 ` steven at gcc dot gnu dot org
2004-09-03 22:58 ` rth at gcc dot gnu dot org
2004-09-07  7:31 ` pinskia at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040811194455.20618.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).