From: Nathan Sidwell <nathan@acm.org>
To: Andreas Schwab <schwab@suse.de>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ PATCH] namespace bindings
Date: Mon, 08 May 2017 14:33:00 -0000 [thread overview]
Message-ID: <fcbca374-477d-92ee-44d7-87206e39f0b0@acm.org> (raw)
In-Reply-To: <mvma86ntuvu.fsf@suse.de>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
On 05/08/2017 08:07 AM, Andreas Schwab wrote:
> On Mai 05 2017, Nathan Sidwell <nathan@acm.org> wrote:
>
>> This cleanup patch kills IDENTIFIER_NAMESPACE_VALUE and replaces
>> {get,set}_namespace_binding with get_namespace_value and set_global_value
>> respectively.
>
> I'm getting this regression on ia64:
>
> FAIL: g++.dg/template/virtual3.C -std=c++11 (test for excess errors)
I'm not seeing this. On an ia64-linux target (hosted on x86_64-linux) I
get the attached output, which is the same as I get on an x86_64-linux
native build.
For the failure mode you describe I'd expect many more test failures to
occur. I wonder if there's some uninitialized variable or something?
nathan
--
Nathan Sidwell
[-- Attachment #2: virt.out --]
[-- Type: text/plain, Size: 1881 bytes --]
virtual3.C:8:8: error: deleted function 'virtual B::~B()'
struct B : A<0>, A<1> // { dg-error "deleted|context" }
^
virtual3.C:5:11: error: overriding non-deleted function 'A<<anonymous> >::~A() [with int <anonymous> = 0]'
virtual ~A(); // { dg-message "non-deleted|private" }
^
virtual3.C:8:8: note: 'virtual B::~B()' is implicitly deleted because the default definition would be ill-formed:
struct B : A<0>, A<1> // { dg-error "deleted|context" }
^
virtual3.C:8:8: error: 'A<<anonymous> >::~A() [with int <anonymous> = 0]' is private within this context
virtual3.C:5:11: note: declared private here
virtual ~A(); // { dg-message "non-deleted|private" }
^
virtual3.C:8:8: error: 'A<<anonymous> >::~A() [with int <anonymous> = 1]' is private within this context
struct B : A<0>, A<1> // { dg-error "deleted|context" }
^
virtual3.C:5:11: note: declared private here
virtual ~A(); // { dg-message "non-deleted|private" }
^
virtual3.C:8:8: error: deleted function 'virtual B::~B()'
struct B : A<0>, A<1> // { dg-error "deleted|context" }
^
virtual3.C:5:11: error: overriding non-deleted function 'A<<anonymous> >::~A() [with int <anonymous> = 1]'
virtual ~A(); // { dg-message "non-deleted|private" }
^
virtual3.C: In constructor 'B::B()':
virtual3.C:10:7: error: 'A<<anonymous> >::~A() [with int <anonymous> = 0]' is private within this context
B() {} // { dg-error "context" }
^
virtual3.C:5:11: note: declared private here
virtual ~A(); // { dg-message "non-deleted|private" }
^
virtual3.C:10:7: error: 'A<<anonymous> >::~A() [with int <anonymous> = 1]' is private within this context
B() {} // { dg-error "context" }
^
virtual3.C:5:11: note: declared private here
virtual ~A(); // { dg-message "non-deleted|private" }
^
next prev parent reply other threads:[~2017-05-08 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 20:25 Nathan Sidwell
2017-05-08 12:41 ` Andreas Schwab
2017-05-08 13:14 ` Nathan Sidwell
2017-05-08 14:33 ` Nathan Sidwell [this message]
2017-05-08 15:25 ` Andreas Schwab
2017-05-08 17:03 ` Nathan Sidwell
2017-05-08 13:06 ` Jason Merrill via gcc-patches
2017-05-08 13:34 ` Nathan Sidwell
2017-05-08 15:54 ` Nathan Sidwell
2017-05-23 19:47 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=fcbca374-477d-92ee-44d7-87206e39f0b0@acm.org \
--to=nathan@acm.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=schwab@suse.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: 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).