public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/30230] New: Incorrect ia64 EH info when an EH region ends in the middle of a bundle Date: Sat, 16 Dec 2006 12:16:00 -0000 [thread overview] Message-ID: <bug-30230-87@http.gcc.gnu.org/bugzilla/> (raw) struct A {}; struct B { virtual ~B(); }; B::~B () {} struct C { void foo (short &, B &); }; struct D { void *d1; C *d2; virtual void virt (void) {} }; struct E { D *e1; B *e2; }; struct F { void bar (void *, B &); }; F *p __attribute__((weak)); volatile int r; void C::foo (short &x, B &) { if (r) throw A (); x = 1; } void F::bar (void *, B &) { throw A (); } void baz (E &x) { short g = 0; B b = *x.e2; x.e1->d2->foo (g, b); if (g) p->bar(x.e1->d1, b); } int main () { F g; D s; E h; p = &g; h.e1 = &s; try { baz (h); } catch (A &) { } return 0; } fails on ia64 at least with gcc trunk and 4.1.1 at -O2. The problem is a br.call not at the end of a bundle where the EH region ends right after it: .mbb ld8 r39 = [r15] br.call.sptk.many b0 = _ZN1F3barEPvR1B# [.LEHE0:] nop 0 ;; As br.call sets rp to the address of the next bundle, when the personality routine is called it doesn't think this call is inside of the .LEHB0 .. .LEHE0 EH region and calls std::terminate. -- Summary: Incorrect ia64 EH info when an EH region ends in the middle of a bundle Product: gcc Version: 4.1.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jakub at gcc dot gnu dot org GCC target triplet: ia64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30230
next reply other threads:[~2006-12-16 12:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-12-16 12:16 jakub at gcc dot gnu dot org [this message] 2006-12-16 13:05 ` [Bug target/30230] " jakub at gcc dot gnu dot org 2006-12-21 12:59 ` jakub at gcc dot gnu dot org 2006-12-21 13:04 ` jakub at gcc dot gnu dot org 2006-12-21 13:07 ` jakub at gcc dot gnu dot org 2007-01-01 21:01 ` wilson at gcc dot gnu dot org 2007-01-10 19:01 ` 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=bug-30230-87@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).