public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Aloysius A. Wild III" <aaw@rincewind.tv> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/4861 Date: Thu, 01 Nov 2001 15:48:00 -0000 [thread overview] Message-ID: <20011112224603.10780.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c++/4861; it has been noted by GNATS. From: "Aloysius A. Wild III" <aaw@rincewind.tv> To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, aaw@rincewind.tv, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c++/4861 Date: Mon, 12 Nov 2001 14:30:58 -0800 This is a multi-part message in MIME format. --------------070207030005010402050701 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4861&database=gcc I've attached an un-preprocessed source file. Note that this problem exists in both 3.0.2 and the current 3.1 snapshot. Ollie --------------070207030005010402050701 Content-Type: text/plain; name="gcc-bug.cpp" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="gcc-bug.cpp" #include <iostream> template<class C> class B { public: ~B() { std::cerr << "Running B::~B()" << std::endl; f(); } virtual void f() { std::cerr << "Running B::f()" << std::endl; } }; class D : public B<int> { public: ~D() { std::cerr << "Running D::~D()" << std::endl; f(); } virtual void f() { std::cerr << "Running D::f()" << std::endl; } }; int main(int argc, char **argv) { D d; return 0; } --------------070207030005010402050701--
reply other threads:[~2001-11-12 22:46 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20011112224603.10780.qmail@sourceware.cygnus.com \ --to=aaw@rincewind.tv \ --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).