public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rodrigc@gcc.gnu.org, dh@digitalbrain.com, simong@oz.agile.tv Subject: Re: target/3947: [MIPS] MIPS multiple inheritance - thunk causes two destructor calls Date: Fri, 29 Nov 2002 17:06:00 -0000 [thread overview] Message-ID: <20021121025343.29837.qmail@sources.redhat.com> (raw) Synopsis: [MIPS] MIPS multiple inheritance - thunk causes two destructor calls State-Changed-From-To: feedback->closed State-Changed-By: bangerth State-Changed-When: Wed Nov 20 18:53:43 2002 State-Changed-Why: No feedback in a long time. Comment to the patch cited in audit trail indicates that the problem has been fixed in 3.1 anyway. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3947
next reply other threads:[~2002-11-21 2:53 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-29 17:06 bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-02-08 14:16 Daniel Jacobowitz 2002-02-08 6:06 Craig Rodrigues 2002-02-08 3:56 Tim Small
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=20021121025343.29837.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=dh@digitalbrain.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=rodrigc@gcc.gnu.org \ --cc=simong@oz.agile.tv \ /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).