From: Jakub Jelinek <jakub@redhat.com>
To: Paolo Carlini <paolo.carlini@oracle.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Nathan Sidwell <nathan@acm.org>,
Jason Merrill <jason@redhat.com>
Subject: Re: [C++ Patch] PR 85070 ("[8/9 Regression] ICE on C++ code: in lazily_declare_fn, at cp/method.c:2409")
Date: Thu, 11 Oct 2018 18:18:00 -0000 [thread overview]
Message-ID: <20181011175917.GE11625@tucnak> (raw)
In-Reply-To: <5bbe72a0-c9c7-4d62-c5b2-74fe5d9098f9@oracle.com>
On Mon, Sep 24, 2018 at 12:48:56PM +0200, Paolo Carlini wrote:
> as explained in the audit trail, the gcc_assert added by Nathan triggers
> during error-recovery too, when add_method correctly returns false because
> it failed to add the method. Thus it seems that we should simply loosen a
> bit the assertion. Tested x86_64-linux.
Testcase fails with check-c++-all:
FAIL: g++.dg/cpp0x/pr85070.C -std=c++17 (test for excess errors)
FAIL: g++.dg/cpp0x/pr85070.C -std=c++2a (test for excess errors)
FAIL: g++.dg/cpp0x/pr85070.C -std=c++17 -fconcepts (test for excess errors)
Any reason why you've used c++14_only effective target, rather than c++14?
If I use the latter, i.e. expect c++17/2a/17 + concepts to behave like c++14
in this case, there are no failures.
Tested with make check-c++-all RUNTESTFLAGS=dg.exp=pr85070.C, ok for trunk?
2018-10-11 Jakub Jelinek <jakub@redhat.com>
PR c++/85070
* g++.dg/cpp0x/pr85070.C: Change effective target for diagnostics from
c++14_only to c++14.
--- gcc/testsuite/g++.dg/cpp0x/pr85070.C.jj 2018-09-25 15:14:43.205270858 +0200
+++ gcc/testsuite/g++.dg/cpp0x/pr85070.C 2018-10-11 19:55:17.795180058 +0200
@@ -4,10 +4,10 @@ struct A;
struct B
{
- constexpr A & operator= (const A &); // { dg-warning "used" "" { target c++14_only } }
+ constexpr A & operator= (const A &); // { dg-warning "used" "" { target c++14 } }
};
-struct A : B // { dg-error "cannot be overloaded" "" { target c++14_only } }
+struct A : B // { dg-error "cannot be overloaded" "" { target c++14 } }
{
using B::operator=;
} a { a = a };
Jakub
next prev parent reply other threads:[~2018-10-11 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 10:58 Paolo Carlini
2018-09-24 15:42 ` Nathan Sidwell
2018-10-11 18:18 ` Jakub Jelinek [this message]
2018-10-11 18:32 ` Paolo Carlini
2018-10-11 18:37 ` Jason Merrill
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=20181011175917.GE11625@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=nathan@acm.org \
--cc=paolo.carlini@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).