public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: middle-end/10415: allocated stack space non optimimal
Date: Tue, 15 Apr 2003 22:46:00 -0000	[thread overview]
Message-ID: <20030415224601.8461.qmail@sources.redhat.com> (raw)

The following reply was made to PR middle-end/10415; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ices.utexas.edu>
To: GrzegorzB <b.grzes@interia.pl>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: middle-end/10415: allocated stack space non optimimal
Date: Tue, 15 Apr 2003 17:43:12 -0500 (CDT)

 > So sorry, I thought it is a bug.
 
 Well, I still think that this is a quality of implementation bug, gcc 
 should be able to do better. I mean, it is not _wrong_ if the compiler 
 allocated too much stack space, it is just wasteful.
 
 There are a number of reports in the bug database about this problem, 
 which also have some documentation about what is the cause for this inside 
 the compiler. Let me close this report, since there are others.
 
 Thanks anyway
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:            bangerth@ices.utexas.edu
                                www: http://www.ices.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-04-15 22:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 22:46 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-15 22:56 bangerth
2003-04-15 22:36 Wolfgang Bangerth
2003-04-15 20:16 Wolfgang Bangerth
2003-04-15 20:16 Wolfgang Bangerth
2003-04-15 18:27 bangerth

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=20030415224601.8461.qmail@sources.redhat.com \
    --to=bangerth@ices.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).