public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: steven@gcc.gnu.org To: Franz.Sirl-kernel@lauterbach.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, sayle@gcc.gnu.org Subject: Re: c++/10031: [3.3/3.4 regression] Bogus error "declaration ... throws different exceptions" Date: Wed, 12 Mar 2003 10:32:00 -0000 [thread overview] Message-ID: <20030312103208.5303.qmail@sources.redhat.com> (raw) Old Synopsis: 3.3/mainline c++ regression New Synopsis: [3.3/3.4 regression] Bogus error "declaration ... throws different exceptions" State-Changed-From-To: open->analyzed State-Changed-By: steven State-Changed-When: Wed Mar 12 10:32:08 2003 State-Changed-Why: Confirmed on powerpc-linux. Sayle's patch for c++/9367 apparently caused this. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10031
next reply other threads:[~2003-03-12 10:32 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-12 10:32 steven [this message] 2003-03-13 19:02 jason 2003-03-18 15:29 sayle
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=20030312103208.5303.qmail@sources.redhat.com \ --to=steven@gcc.gnu.org \ --cc=Franz.Sirl-kernel@lauterbach.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=sayle@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).