From: hjl@lucon.org (H.J. Lu)
To: law@cygnus.com
Cc: jason@cygnus.com, egcs@cygnus.com
Subject: EH in egcs
Date: Sun, 26 Oct 1997 12:39:00 -0000 [thread overview]
Message-ID: <m0xPZNc-0004edC@ocean.lucon.org> (raw)
In-Reply-To: <25297.877890294@hurl.cygnus.com>
Although EH is much better than before, it still needs some improvement,
especially what happens after the exception is caught. There are 2
test cases which show the problem. That is nested throw/catch doesn't
work. That is because __eh_value/__eh_type are used throughout
EH and the new ones will override the old ones. I was wondering if
we could do this in the catch region:
Treat the caught exception as a local variable. That is make
catch (type caught)
{
}
equivalent to
foo ()
{
type caught;
}
Can we use __eh_value/__eh_type to make it to work? After that,
caught will be handled just like any other local variables.
If there is another exception thrown inside foo (), caught
will be cleared appropriately. Otherwise, it will be cleared
when exception is out of scope.
--
H.J. Lu (hjl@gnu.ai.mit.edu)
next prev parent reply other threads:[~1997-10-26 12:39 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-23 20:19 (971023) i386-linux-gnulibc1 gcc/g++ test results Mumit Khan
1997-10-23 21:30 ` (971023) Addendum: i386-linux-gnulibc1 g++ " Mumit Khan
1997-10-23 23:12 ` H.J. Lu
1997-10-24 1:43 ` Theodore Papadopoulo
1997-11-01 21:53 ` Jeffrey A Law
1997-11-02 10:26 ` Thomas Weise
1997-11-02 10:30 ` Thomas Weise
1997-11-02 19:06 ` Jeffrey A Law
1997-11-15 4:58 ` DWARF EH problem (was: Re: (971023) Addendum: i386-linux-gnulibc1 g++ test results) Thomas Weise
[not found] ` <199710240843.KAA07400.cygnus.egcs@mururoa.inria.fr>
1997-10-24 9:35 ` (971023) Addendum: i386-linux-gnulibc1 g++ test results Jason Merrill
1997-10-24 10:46 ` Robert Lipe
1997-10-24 10:59 ` Mumit Khan
1997-10-24 12:11 ` EH bug in Makefile.in H.J. Lu
1997-10-24 14:30 ` Mumit Khan
1997-10-24 14:35 ` H.J. Lu
1997-10-25 9:49 ` Mumit Khan
1997-10-25 20:34 ` Joe Buck
1997-10-26 0:56 ` Mumit Khan
1997-10-26 16:30 ` [ECGS] " chip
[not found] ` <9710260755.AA26107.cygnus.egcs@modi.xraylith.wisc.edu>
1997-10-26 1:17 ` Jason Merrill
1997-10-26 9:49 ` Jeffrey A Law
1997-10-25 11:19 ` acs
1997-10-25 12:18 ` H.J. Lu
1997-10-24 16:16 ` Robert Lipe
1997-10-26 10:22 ` Jeffrey A Law
1997-10-26 12:39 ` H.J. Lu [this message]
1997-10-26 12:39 ` EH in egcs Jason Merrill
1997-10-26 16:21 ` H.J. Lu
1997-10-26 19:34 ` Alexandre Oliva
1997-10-26 19:34 ` H.J. Lu
1997-10-26 18:21 ` Alexandre Oliva
1997-10-26 20:44 ` Oleg Krivosheev
1997-10-27 10:50 ` SGI STL patch Oleg Krivosheev
1997-10-27 11:57 ` Joe Buck
1997-10-27 12:00 ` Jason Merrill
1997-10-27 16:30 ` Matt Austern
1997-10-28 15:42 ` Oleg Krivosheev
1997-10-28 17:57 ` Matt Austern
1997-10-28 15:58 ` Oleg Krivosheev
1997-10-28 17:57 ` Matt Austern
1997-10-27 12:24 ` Alexander Stepanov
1997-10-23 22:55 ` (971023) i386-linux-gnulibc1 gcc/g++ test results H.J. Lu
1997-10-27 16:22 EH in egcs Mike Stump
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=m0xPZNc-0004edC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@cygnus.com \
--cc=jason@cygnus.com \
--cc=law@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).