Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Wei-min Pan <weimin.pan@oracle.com>
Cc: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH v3 PR gdb/16841] virtual inheritance via typedef cannot find base
Date: Fri, 05 Oct 2018 14:02:00 -0000	[thread overview]
Message-ID: <87sh1kh4py.fsf@tromey.com> (raw)
In-Reply-To: <53170edb-bed8-1c42-2d55-93ee622d0822@oracle.com> (Wei-min Pan's	message of "Thu, 4 Oct 2018 16:51:16 -0700")

>>>>> ">" == Wei-min Pan <weimin.pan@oracle.com> writes:

>> Thank you for the clarification. I have expanded both virtbase2.cc
>> and virtbase2.exp (attached) to test the multiple inheritance case.

Thank you for persevering.  Please check in the patch.

Tom


      reply	other threads:[~2018-10-05 14:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-13  1:39 Weimin Pan
2018-09-14 18:26 ` Simon Marchi
2018-09-14 21:49   ` Weimin Pan
2018-09-18 11:59 ` Tom Tromey
2018-09-18 23:26   ` Weimin Pan
2018-10-04 22:20     ` Tom Tromey
2018-10-04 23:51       ` Wei-min Pan
2018-10-05 14:02         ` Tom Tromey [this message]

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=87sh1kh4py.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=weimin.pan@oracle.com \
    /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: link
Be 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