public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/101782] [12 regression] Excess errors in g++.dg/cpp2a/concepts-pr67774.C after r12-2729 Date: Thu, 05 Aug 2021 14:17:30 +0000 [thread overview] Message-ID: <bug-101782-4-rxH8dDmHj8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101782-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101782 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:7b1de3eb9ed3f8dde54732d88520292c5ad1157d commit r12-2766-g7b1de3eb9ed3f8dde54732d88520292c5ad1157d Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Aug 5 13:34:00 2021 +0100 libstdc++: Move attributes that follow requires-clauses [PR101782] As explained in the PR, the grammar in the Concepts TS means that a [ token following a requires-clause is parsed as part of the logical-or-expression rather than the start of an attribute. That makes the following ill-formed when using -fconcepts-ts: template<typename T> requires foo<T> [[nodiscard]] int f(T); This change moves all attributes that follow a requires-clause to the end of the function declarator. Signed-off-by: Jonathan Wakely <jwakely@redhat.com> libstdc++-v3/ChangeLog: PR libstdc++/101782 * include/bits/ranges_base.h (ranges::begin, ranges::end) (ranges::rbegin, ranges::rend, ranges::size, ranges::ssize) (ranges::empty, ranges::data): Move attribute to the end of the declarator. * include/bits/stl_iterator.h (__gnu_cxx::__normal_iterator) (common_iterator): Likewise for non-member operator functions. * include/std/ranges (views::all, views::filter) (views::transform, views::take, views::take_while, views::drop) (views::drop_while, views::join, views::lazy_split) (views::split, views::counted, views::common, views::reverse) (views::elements): Likewise. * testsuite/std/ranges/access/101782.cc: New test.
next prev parent reply other threads:[~2021-08-05 14:17 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-04 20:23 [Bug testsuite/101782] New: " seurer at gcc dot gnu.org 2021-08-04 21:21 ` [Bug testsuite/101782] " redi at gcc dot gnu.org 2021-08-04 22:29 ` [Bug c++/101782] " redi at gcc dot gnu.org 2021-08-04 22:35 ` redi at gcc dot gnu.org 2021-08-05 10:31 ` [Bug testsuite/101782] " redi at gcc dot gnu.org 2021-08-05 11:14 ` jakub at gcc dot gnu.org 2021-08-05 14:17 ` cvs-commit at gcc dot gnu.org [this message] 2021-08-05 14:28 ` [Bug libstdc++/101782] " redi at gcc dot gnu.org 2021-08-05 18:01 ` cvs-commit at gcc dot gnu.org
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=bug-101782-4-rxH8dDmHj8@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).