public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: nathan@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nathan@gcc.gnu.org, nobody@gcc.gnu.org, stefan@space.twc.de Subject: Re: c++/3145: virtual inheritance still creates wrong code Date: Thu, 14 Jun 2001 03:59:00 -0000 [thread overview] Message-ID: <20010614105907.27576.qmail@sourceware.cygnus.com> (raw) Synopsis: virtual inheritance still creates wrong code Responsible-Changed-From-To: nathan->unassigned Responsible-Changed-By: nathan Responsible-Changed-When: Thu Jun 14 03:59:06 2001 Responsible-Changed-Why: Partially fixed. remaining faults in build_vbase_path, which is longstanding. 2001-06-14 Nathan Sidwell <nathan@codesourcery.com> * class.c (dfs_accumulate_vtbl_inits): For case 2 & 3, make sure we've not emerged from the hierarchy of RTTI_BINFO on reaching a non-virtual base. 2001-06-14 Nathan Sidwell <nathan@codesourcery.com> * g++.old-deja/g++.abi/vbase8-9.C: New test. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3145&database=gcc
next reply other threads:[~2001-06-14 3:59 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-14 3:59 nathan [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-11-20 17:53 nathan 2001-11-20 17:46 nathan 2001-07-17 7:35 nathan 2001-06-13 1:47 nathan 2001-06-12 14:46 stefan
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=20010614105907.27576.qmail@sourceware.cygnus.com \ --to=nathan@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=stefan@space.twc.de \ /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).