From: Christophe Lyon <christophe.lyon@linaro.org>
To: Jason Merrill <jason@redhat.com>
Cc: Romain Geissler <romain.geissler@gmail.com>,
gcc-patches List <gcc-patches@gcc.gnu.org>,
Andrew Sutton <andrew.n.sutton@gmail.com>
Subject: Re: C++ PATCH to merge concepts-cxx2a branch
Date: Fri, 11 Oct 2019 08:19:00 -0000 [thread overview]
Message-ID: <CAKdteOYdKLSsXERxqMum1eOJF9hNNNiiUcbVDTkjdKp3X_2D-w@mail.gmail.com> (raw)
In-Reply-To: <CADzB+2kaaPevkxYV3Y4gUOt4HxHkW745OCp29JiA9b2EXhs38Q@mail.gmail.com>
On Thu, 10 Oct 2019 at 23:38, Jason Merrill <jason@redhat.com> wrote:
> On Thu, Oct 10, 2019 at 3:55 PM Christophe Lyon <
> christophe.lyon@linaro.org> wrote:
>
>> On Thu, 10 Oct 2019 at 01:44, Romain Geissler <romain.geissler@gmail.com>
>> wrote:
>>
>>> Le mer. 9 oct. 2019 à 19:20, Jason Merrill <jason@redhat.com> a écrit :
>>> >
>>> > Andrew has done a lot of work to update the GCC implementation of C++
>>> > concepts to conform to the upcoming C++20 standard, which clarifies,
>>> > removes, and changes various aspects of the earlier concepts TS. It
>>> can
>>> > still use some polishing, but other stage 1 projects are waiting for it
>>> > to land on trunk and it's already a big improvement from what's
>>> > currently there, so I'm going to go ahead and merge it now.
>>> >
>>> > Tested x86_64-pc-linux-gnu, applying to trunk.
>>>
>>> Hi Jason,
>>>
>>> This is a very good news to see preliminary concept support being
>>> merged in the trunk :)
>>>
>>> However for me, this caused the following bootstrap failure:
>>>
>>> In file included from /workdir/src/gcc-10.0.0/gcc/cp/cp-lang.c:24:
>>> /workdir/src/gcc-10.0.0/gcc/cp/cp-tree.h: In function 'tree_node*
>>> template_info_decl_check(const_tree, const char*, int, const char*)':
>>> /workdir/src/gcc-10.0.0/gcc/cp/cp-tree.h:3368:3: error:
>>> 'tree_check_failed' was not declared in this scope
>>> tree_check_failed (t, f, l, fn,
>>> ^~~~~~~~~~~~~~~~~
>>> /workdir/src/gcc-10.0.0/gcc/cp/cp-tree.h:3368:3: note: suggested
>>> alternative: 'vec_check_alloc'
>>> tree_check_failed (t, f, l, fn,
>>> ^~~~~~~~~~~~~~~~~
>>> vec_check_alloc
>>> make[2]: *** [Makefile:1118: cp/cp-lang.o] Error 1
>>>
>>>
>> On arm, this is causing:
>> FAIL: g++.dg/ext/arm-fp16/arm-fp16-ops-1.C -std=gnu++2a (test for
>> excess errors)
>> Excess errors:
>> /gcc/testsuite/g++.dg/ext/arm-fp16/arm-fp16-ops.h:31:10: warning: '++'
>> expression of 'volatile'-qualified type is deprecated [-Wvolatile]
>>
>
> These would be due to
>
> 2019-08-28 Marek Polacek <polacek@redhat.com>
>
> Implement P1152R4: Deprecating some uses of volatile.
> PR c++/91361
> * cp-gimplify.c (cp_fold): Set TREE_THIS_VOLATILE.
> * decl.c (grokdeclarator): Warn about a volatile-qualified
> structured
> binding and return type.
> (grokparms): Warn about a volatile-qualified function parameter.
> * expr.c (mark_use) <case MODIFY_EXPR>: Emit a -Wvolatile warning.
> * typeck.c (cp_build_unary_op): Emit a -Wvolatile warning for pre
> and
> post ++/-- on a volatile operand.
> (genericize_compound_lvalue): Use a better location. Don't lose
> TREE_THIS_VOLATILE.
> (cp_build_modify_expr): Emit a -Wvolatile warning for a compound
> assignment whose LHS is volatile-qualified. Build the assignment
> with
> a more precise location.
>
>
You are probably right. I replied here because gisect flagged your patch.
> and not the concepts merge. You probably want to turn off -Wvolatile for
> affected tests.
>
Isn't the warning valid in this case? (ie. shouldn't we fix arm-fp16-ops.h
instead?)
>
> and also:
>
>> FAIL: g++.dg/cpp2a/constexpr-dtor3.C -std=c++2a (test for excess errors)
>> Excess errors:
>> /gcc/testsuite/g++.dg/cpp2a/constexpr-dtor3.C:152:12: in 'constexpr'
>> expansion of '(& w13)->W7::~W7()'
>>
>
> This also seems unrelated, but I'll take a look.
>
> Thanks, I must confess I didn't bisect for this one. It appeared in the
same range of commits
as the other regressions above: between r276750 and r276786 included.
Thanks
Christophe
> Jason
>
>
next prev parent reply other threads:[~2019-10-11 7:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 17:28 Jason Merrill
2019-10-10 1:56 ` Romain Geissler
2019-10-10 19:56 ` Christophe Lyon
2019-10-10 21:45 ` Jason Merrill
2019-10-11 8:19 ` Christophe Lyon [this message]
2019-10-11 8:33 ` [PATCH] Fix constexpr-dtor3.C FAIL on arm Jakub Jelinek
2019-10-11 20:18 ` Jason Merrill
2019-10-16 16:35 ` Jakub Jelinek
2019-10-16 20:36 ` Jason Merrill
2019-10-16 21:03 ` Jason Merrill
2019-10-17 22:57 ` Jakub Jelinek
2019-10-22 20:55 ` 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=CAKdteOYdKLSsXERxqMum1eOJF9hNNNiiUcbVDTkjdKp3X_2D-w@mail.gmail.com \
--to=christophe.lyon@linaro.org \
--cc=andrew.n.sutton@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=romain.geissler@gmail.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).