From: Thomas Weise <tom@zaphod.wh9.tu-dresden.de>
To: Jason Merrill <jason@cygnus.com>
Cc: egcs-bugs@cygnus.com, egcs@cygnus.com
Subject: Re: EH unwind bug
Date: Tue, 02 Dec 1997 09:56:00 -0000 [thread overview]
Message-ID: <34844A93.5E91@zaphod.wh9.tu-dresden.de> (raw)
In-Reply-To: <u9btz0cs9q.fsf@yorick.cygnus.com>
>
> > stackObj::~stackObj()
> > stackObj::~stackObj()
> > IOT trap/Abort
>
> ./:
> Mon Dec 1 19:48:53 1997 Jason Merrill <jason@yorick.cygnus.com>
>
> * except.c (expand_fixup_region_end): New fn.
> * stmt.c (expand_cleanups): Use it to protect fixups.
>
> cp/:
> Mon Dec 1 19:32:43 1997 Jason Merrill <jason@yorick.cygnus.com>
>
> * exception.cc (__cp_pop_exception): Lose handler arg.
> * except.c (do_pop_exception): Likewise.
> (push_eh_cleanup): Let the cleanup mechanism supply the handler.
> (expand_end_catch_block): Likewise.
[ http://www.cygnus.com/ml/egcs-bugs/1997-Dec/0008.html ]
I've assigned this patch to egcs971201 and it fixes the testcase.
Unfortunately I get a new internal error, please see the testcase below.
tom@hermes:/home/tom > g++ -v
Reading specs from
/usr/local/lib/gcc-lib/i486-pc-linux-gnulibc1/egcs-2.90.20/specs
gcc version egcs-2.90.20 971201 (gcc2-970802 experimental)
tom@hermes:/home/tom > g++ bug3.cc
bug3.cc: In method `void foo::op(unsigned char = false)':
bug3.cc:33: Internal compiler error.
bug3.cc:33: Please submit a full bug report to `egcs-bugs@cygnus.com'.
next parent reply other threads:[~1997-12-02 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <347B076D.6F1CEC10.cygnus.egcs.bugs@zaphod.wh9.tu-dresden.de>
[not found] ` <u9btz0cs9q.fsf@yorick.cygnus.com>
1997-12-02 9:56 ` Thomas Weise [this message]
1997-12-03 0:21 ` Jason Merrill
1997-12-03 5:46 ` Thomas Weise
1997-12-03 8:23 ` Jeffrey A Law
[not found] <347B307E.80D08A44.cygnus.egcs@zaphod.wh9.tu-dresden.de>
1997-11-26 6:10 ` Jason Merrill
1997-11-25 16:09 Thomas Weise
-- strict thread matches above, loose matches on Subject: below --
1997-11-25 8:14 Thomas Weise
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=34844A93.5E91@zaphod.wh9.tu-dresden.de \
--to=tom@zaphod.wh9.tu-dresden.de \
--cc=egcs-bugs@cygnus.com \
--cc=egcs@cygnus.com \
--cc=jason@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).