public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Geert Bosch" <bosch@gnat.com>
To: "Anthony Green" <green@cygnus.com>,
	"Earl S. Harris, Jr." <esharris@mitre.org>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Catching stack overflow errors
Date: Sun, 13 Aug 2000 13:45:00 -0000	[thread overview]
Message-ID: <20000813204345.858AF34D80@nile.gnat.com> (raw)

On 11 Aug 2000 06:30:07 -0700, Anthony Green wrote:

  It is also important for other languages supported by GCC.  Java
  implementations are required to throw exceptions when a stack is blown
  but gcj currently ignores this.

One of the weaknesses currently in GCC is that under certain
circumstances the fixed portion of the stack frame can get
larger than the amount of storage which is guaranteed to be
available when the function is called (typically 1 page, or 4kB)
Even though there is a warning "stack frame too large, reduce
number of locals", this is not that helpful especially if many
of the locals are temporaries introduced by the compiler during
expansion of certain constructs.

GCC has some hacks that try to allocate anyting big in the dynamic
portion of the frame, but this only masks the problems and leads
to unnecessarily inefficient code.

  -Geert


             reply	other threads:[~2000-08-13 13:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-13 13:45 Geert Bosch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-08-04 13:42 Earl S. Harris, Jr.
2000-08-04 14:04 ` David Edelsohn
2000-08-07  5:44   ` Earl S. Harris, Jr.
2000-08-11  6:30     ` Anthony Green
2000-08-11 15:57       ` Geoff Keating

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=20000813204345.858AF34D80@nile.gnat.com \
    --to=bosch@gnat.com \
    --cc=esharris@mitre.org \
    --cc=gcc@gcc.gnu.org \
    --cc=green@cygnus.com \
    /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).