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 c++/90333] [9/10/11 Regression] Can't apply attributes to lambdas with trailing returns Date: Sat, 27 Feb 2021 20:44:36 +0000 [thread overview] Message-ID: <bug-90333-4-8P6ToGutDX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-90333-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90333 --- Comment #15 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:5d9d6c1cd8d9f0e057b4a7a849bc765e2109137c commit r11-7430-g5d9d6c1cd8d9f0e057b4a7a849bc765e2109137c Author: Jason Merrill <jason@redhat.com> Date: Fri Feb 26 05:45:02 2021 -0500 c++: Allow GNU attributes before lambda -> [PR90333] In my 9.3/10 patch for 90333 I allowed attributes between [] and (), and after the trailing return type, but not in the place that GCC 8 expected them, and we've gotten several bug reports about that. So let's allow them there, as well. gcc/cp/ChangeLog: PR c++/90333 * parser.c (cp_parser_lambda_declarator_opt): Accept GNU attributes between () and ->. gcc/testsuite/ChangeLog: PR c++/90333 * g++.dg/ext/attr-lambda3.C: New test.
next prev parent reply other threads:[~2021-02-27 20:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-90333-4@http.gcc.gnu.org/bugzilla/> 2020-06-25 23:34 ` [Bug c++/90333] [9 " ttimo at valvesoftware dot com 2021-02-26 4:12 ` [Bug c++/90333] [9/10/11 " jason at gcc dot gnu.org 2021-02-26 4:13 ` jason at gcc dot gnu.org 2021-02-26 4:15 ` jason at gcc dot gnu.org 2021-02-27 20:43 ` cvs-commit at gcc dot gnu.org 2021-02-27 20:43 ` cvs-commit at gcc dot gnu.org 2021-02-27 20:44 ` cvs-commit at gcc dot gnu.org [this message] 2021-02-28 5:39 ` jason 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-90333-4-8P6ToGutDX@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).