public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/8117: [3.2 regression] member function pointers and multiple inheritance Date: Fri, 13 Dec 2002 16:56:00 -0000 [thread overview] Message-ID: <20021214005601.17092.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8117; it has been noted by GNATS. From: Janis Johnson <janis187@us.ibm.com> To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, yuvalk@mainsoft.com, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c++/8117: [3.2 regression] member function pointers and multiple inheritance Date: Fri, 13 Dec 2002 16:56:54 -0800 This regression from 3.0.4 has been fixed on the mainline but still exists in the 3.2 branch. The bug showed up when this patch was added: 2001-11-28 Nathan Sidwell <nathan@codesourcery.com> * cp-tree.h (UNIQUELY_DERIVED_FROM_P): Use lookup base. * call.c (standard_conversion): Use lookup_base. * class.c (strictly_overrides): Likewise. * cvt.c (build_up_reference): Adjust comment. * init.c (build_member_call): Reformat. * search.c (get_binfo): Remove. * tree.c (binfo_value): Remove. * typeck.c (build_static_cast): Use lookup_base. * typeck2.c (binfo_or_else): Use lookup_base. The bug went away on the mainline when this patch was added: 2002-10-25 Mark Mitchell <mark@codesourcery.com> * call.c (build_over_call): Use DECL_CONTEXT, not * class.c (modify_vtable_entry): Don't mess with * cp-tree.h (lang_type_class): Remove vsize. * pt.c (build_template_decl): Don't set it. * typeck.c (expand_ptrmemfunc_cst): Don't use it. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8117
next reply other threads:[~2002-12-14 0:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-13 16:56 Janis Johnson [this message] 2003-04-25 19:43 jbuck
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=20021214005601.17092.qmail@sources.redhat.com \ --to=janis187@us.ibm.com \ --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).