public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/50: problem calling destructor on typedef of int within namespace Date: Wed, 01 Jan 2003 18:46:00 -0000 [thread overview] Message-ID: <20030101184601.20942.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/50; it has been noted by GNATS. From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> To: neil@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, martin@loewis.home.cs.tu-berlin.de, nobody@gcc.gnu.org, paul.thomas@eds.com, gcc-gnats@gcc.gnu.org Cc: Subject: Re: c++/50: problem calling destructor on typedef of int within namespace Date: Wed, 1 Jan 2003 19:42:21 +0100 On Wed, Jan 01, 2003 at 12:17:02AM -0000, neil@gcc.gnu.org wrote: > Synopsis: problem calling destructor on typedef of int within namespace > > State-Changed-From-To: suspended->closed > State-Changed-By: neil > State-Changed-When: Tue Dec 31 16:17:01 2002 > State-Changed-Why: > Fixed for 3.4. Hm, there are two code snippets in that report, one indeed compiles for me, the other one gives an ICE now. See PR 9099 for a reduced example but shouldn't we keep the report open until we can verify that both code snippets compile? regards Christian -- THAT'S ALL FOLKS!
next reply other threads:[~2003-01-01 18:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-01 18:46 Christian Ehrhardt [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-31 16:17 neil 2001-11-16 12:56 nathan 2001-11-16 11:06 nathan
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=20030101184601.20942.qmail@sources.redhat.com \ --to=ehrhardt@mathematik.uni-ulm.de \ --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).