From: Jason Merrill <jason@redhat.com>
To: Marek Polacek <polacek@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v2] c++: Fix C++11 attribute propagation [PR106712]
Date: Mon, 29 Aug 2022 17:16:15 -0400 [thread overview]
Message-ID: <07135428-8d51-69c2-3631-ca126b15c378@redhat.com> (raw)
In-Reply-To: <Yw0a/M/AsXSKF/Ng@redhat.com>
On 8/29/22 16:01, Marek Polacek wrote:
> On Mon, Aug 29, 2022 at 01:32:29PM -0400, Jason Merrill wrote:
>> On 8/26/22 19:01, Marek Polacek wrote:
>>> When we have
>>>
>>> [[noreturn]] int fn1 [[nodiscard]](), fn2();
>>>
>>> "noreturn" should apply to both fn1 and fn2 but "nodiscard" only to fn1:
>>> [dcl.pre]/3: "The attribute-specifier-seq appertains to each of
>>> the entities declared by the declarators of the init-declarator-list."
>>> [dcl.spec.general]: "The attribute-specifier-seq affects the type
>>> only for the declaration it appears in, not other declarations involving
>>> the same type."
>>>
>>> As Ed Catmur correctly analyzed, this is because, for the test above,
>>> we call start_decl with prefix_attributes=noreturn, but this line:
>>>
>>> attributes = attr_chainon (attributes, prefix_attributes);
>>>
>>> results in attributes == prefix_attributes, because chainon sees
>>> that attributes is null so it just returns prefix_attributes. Then
>>> in grokdeclarator we reach
>>>
>>> *attrlist = attr_chainon (*attrlist, declarator->std_attributes);
>>>
>>> which modifies prefix_attributes so now it's "noreturn, nodiscard"
>>> and so fn2 is wrongly marked nodiscard as well. Fixed by copying
>>> prefix_attributes.
>>
>> How about reversing the order of arguments to the call in grokdeclarator, so
>> that the prefix attributes can remain shared at the end of the list?
>
> Thanks, that seems like a cheaper solution. It works because this way
> we tack the prefix attributes onto ->std_attributes, avoiding modifying
> prefix_attributes.
>
> Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
OK.
> -- >8 --
> When we have
>
> [[noreturn]] int fn1 [[nodiscard]](), fn2();
>
> "noreturn" should apply to both fn1 and fn2 but "nodiscard" only to fn1:
> [dcl.pre]/3: "The attribute-specifier-seq appertains to each of
> the entities declared by the declarators of the init-declarator-list."
> [dcl.spec.general]: "The attribute-specifier-seq affects the type
> only for the declaration it appears in, not other declarations involving
> the same type."
>
> As Ed Catmur correctly analyzed, this is because, for the test above,
> we call start_decl with prefix_attributes=noreturn, but this line:
>
> attributes = attr_chainon (attributes, prefix_attributes);
>
> results in attributes == prefix_attributes, because chainon sees
> that attributes is null so it just returns prefix_attributes. Then
> in grokdeclarator we reach
>
> *attrlist = attr_chainon (*attrlist, declarator->std_attributes);
>
> which modifies prefix_attributes so now it's "noreturn, nodiscard"
> and so fn2 is wrongly marked nodiscard as well. Fixed by reversing
> the order of arguments to attr_chainon. That way, we tack the prefix
> attributes onto ->std_attributes, avoiding modifying prefix_attributes.
>
> PR c++/106712
>
> gcc/cp/ChangeLog:
>
> * decl.cc (grokdeclarator): Reverse the order of arguments to
> attr_chainon.
>
> gcc/testsuite/ChangeLog:
>
> * g++.dg/cpp0x/gen-attrs-77.C: New test.
> ---
> gcc/cp/decl.cc | 2 +-
> gcc/testsuite/g++.dg/cpp0x/gen-attrs-77.C | 17 +++++++++++++++++
> 2 files changed, 18 insertions(+), 1 deletion(-)
> create mode 100644 gcc/testsuite/g++.dg/cpp0x/gen-attrs-77.C
>
> diff --git a/gcc/cp/decl.cc b/gcc/cp/decl.cc
> index d46a347a6c7..b72b2a8456b 100644
> --- a/gcc/cp/decl.cc
> +++ b/gcc/cp/decl.cc
> @@ -13474,7 +13474,7 @@ grokdeclarator (const cp_declarator *declarator,
> /* [dcl.meaning]/1: The optional attribute-specifier-seq following
> a declarator-id appertains to the entity that is declared. */
> if (declarator->std_attributes != error_mark_node)
> - *attrlist = attr_chainon (*attrlist, declarator->std_attributes);
> + *attrlist = attr_chainon (declarator->std_attributes, *attrlist);
> else
> /* We should have already diagnosed the issue (c++/78344). */
> gcc_assert (seen_error ());
> diff --git a/gcc/testsuite/g++.dg/cpp0x/gen-attrs-77.C b/gcc/testsuite/g++.dg/cpp0x/gen-attrs-77.C
> new file mode 100644
> index 00000000000..2c41c62f33b
> --- /dev/null
> +++ b/gcc/testsuite/g++.dg/cpp0x/gen-attrs-77.C
> @@ -0,0 +1,17 @@
> +// PR c++/106712
> +// { dg-do compile { target c++11 } }
> +
> +[[noreturn]] int f1 [[nodiscard]](), f2 ();
> +[[nodiscard]] int f3 (), f4 ();
> +int f5 [[nodiscard]](), f6 ();
> +
> +int
> +main ()
> +{
> + f1 (); // { dg-warning "ignoring" }
> + f2 ();
> + f3 (); // { dg-warning "ignoring" }
> + f4 (); // { dg-warning "ignoring" }
> + f5 (); // { dg-warning "ignoring" }
> + f6 ();
> +}
>
> base-commit: 60d1d296b42b22b08d4eaa38bea02100c07261ac
prev parent reply other threads:[~2022-08-29 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 23:01 [PATCH] " Marek Polacek
2022-08-29 17:32 ` Jason Merrill
2022-08-29 20:01 ` [PATCH v2] " Marek Polacek
2022-08-29 21:16 ` Jason Merrill [this message]
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=07135428-8d51-69c2-3631-ca126b15c378@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=polacek@redhat.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).