public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@acm.org>
To: Jason Merrill <jason@redhat.com>,  GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [C++/66443] virtual base of abstract class
Date: Fri, 17 Jul 2015 20:12:00 -0000	[thread overview]
Message-ID: <55A95E99.7020309@acm.org> (raw)
In-Reply-To: <55A95AB9.6050105@redhat.com>

On 07/17/15 15:42, Jason Merrill wrote:
> On 07/08/2015 10:50 AM, Nathan Sidwell wrote:
>> On 06/30/15 19:21, Nathan Sidwell wrote:
>>> On 06/30/15 00:19, Jason Merrill wrote:
>>>> On 06/29/2015 06:57 PM, Nathan Sidwell wrote:
>>>>>     * method.c (synthesized_method_walk): Skip virtual bases of
>>>>>     abstract classes in C++14 mode.
>>>>
>>>> Let's not limit this to C++14 mode; most DRs apply to earlier
>>>> standards as well.
>>
>> curiously opening it up leads to some test failures related to
>> determining the exception specifier for implicit ctors and dtors.  Not
>> had time to investigate that yet ...
>
> If C++98 mode is problematic, we can limit this to C++11 and up.

I'm not yet sure.  The failure mode I saw surprised me, and suggests there's 
something wrong with the patch.  Sadly, I've got interrupted by other stuff.

nathan

  reply	other threads:[~2015-07-17 19:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30  0:10 [C++/66443] Nathan Sidwell
2015-06-30  4:24 ` [C++/66443] Jason Merrill
2015-06-30 23:24   ` [C++/66443] Nathan Sidwell
2015-07-08 14:50     ` [C++/66443] virtual base of abstract class Nathan Sidwell
2015-07-17 19:57       ` Jason Merrill
2015-07-17 20:12         ` Nathan Sidwell [this message]
2015-08-01 23:31           ` Nathan Sidwell
2015-08-03  3:44             ` Jason Merrill
2015-08-03 13:20               ` Nathan Sidwell

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=55A95E99.7020309@acm.org \
    --to=nathan@acm.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).