public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Michael Veksler <veksler@il.ibm.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/6350: 3.1 crash on multiple-catch + overriden virtual functions Date: Sun, 21 Apr 2002 00:06:00 -0000 [thread overview] Message-ID: <20020421070601.12501.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/6350; it has been noted by GNATS. From: Michael Veksler <veksler@il.ibm.com> To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, veksler@il.ibm.com, gcc-bugs@gcc.gnu.org Cc: Subject: Re: c++/6350: 3.1 crash on multiple-catch + overriden virtual functions Date: Sun, 21 Apr 2002 10:00:43 +0300 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6350 This is a serious regression from gcc-3.0.x, it renders gcc-3.1 unusable for me. This bug means that 3.1 does not support exceptions (if you have a virtual function with more than one "catch", gcc will crash). Can I help in any way to make it fixed before official 3.1.0 ? Thanks Michael
next reply other threads:[~2002-04-21 7:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-21 0:06 Michael Veksler [this message] 2002-04-22 5:48 gerald 2002-04-22 13:16 Michael Veksler 2002-04-22 13:28 mmitchel 2002-04-22 17:46 Richard Henderson
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=20020421070601.12501.qmail@sources.redhat.com \ --to=veksler@il.ibm.com \ --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: 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).