From: Jason Merrill <jason@redhat.com>
To: Nathaniel Shead <nathanieloshead@gmail.com>,
Patrick Palka <ppalka@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] c++: Fix ICE with parameter pack of decltype(auto) [PR103497]
Date: Thu, 29 Jun 2023 13:43:07 -0400 [thread overview]
Message-ID: <5d7ada85-ccaa-bc07-b625-20fdc5dc924c@redhat.com> (raw)
In-Reply-To: <ZJbukJluJlp23xw5@Thaum.localdomain>
On 6/24/23 09:24, Nathaniel Shead wrote:
> On Fri, Jun 23, 2023 at 11:59:51AM -0400, Patrick Palka wrote:
>> Hi,
>>
>> On Sat, 22 Apr 2023, Nathaniel Shead via Gcc-patches wrote:
>>
>>> Bootstrapped and tested on x86_64-pc-linux-gnu.
>>>
>>> -- 8< --
>>>
>>> This patch raises an error early when the decltype(auto) specifier is
>>> used as a parameter of a function. This prevents any issues with an
>>> unexpected tree type later on when performing the call.
>>
>> Thanks very much for the patch! Some minor comments below.
>>
>>>
>>> PR 103497
>>
>> We should include the bug component name when referring to the PR in the
>> commit message (i.e. PR c++/103497) so that upon pushing the patch the
>> post-commit hook automatically adds a comment to the PR reffering to the
>> commit. I could be wrong but AFAIK the hook only performs this when the
>> component name is included.
>
> Thanks for the review! Fixed.
>
>>>
>>> gcc/cp/ChangeLog:
>>>
>>> * parser.cc (cp_parser_simple_type_specifier): Add check for
>>> decltype(auto) as function parameter.
>>>
>>> gcc/testsuite/ChangeLog:
>>>
>>> * g++.dg/pr103497.C: New test.
>>>
>>> Signed-off-by: Nathaniel Shead <nathanieloshead@gmail.com>
>>> ---
>>> gcc/cp/parser.cc | 10 ++++++++++
>>> gcc/testsuite/g++.dg/pr103497.C | 7 +++++++
>>> 2 files changed, 17 insertions(+)
>>> create mode 100644 gcc/testsuite/g++.dg/pr103497.C
>>>
>>> diff --git a/gcc/cp/parser.cc b/gcc/cp/parser.cc
>>> index e5f032f2330..1415e07e152 100644
>>> --- a/gcc/cp/parser.cc
>>> +++ b/gcc/cp/parser.cc
>>> @@ -19884,6 +19884,16 @@ cp_parser_simple_type_specifier (cp_parser* parser,
>>> && cp_lexer_peek_nth_token (parser->lexer, 2)->type != CPP_SCOPE)
>>> {
>>> type = saved_checks_value (token->u.tree_check_value);
>>> + /* Within a function parameter declaration, decltype(auto) is always an
>>> + error. */
>>> + if (parser->auto_is_implicit_function_template_parm_p
>>> + && TREE_CODE (type) == TEMPLATE_TYPE_PARM
>>
>> We could check is_auto (type) here instead, to avoid any confusion with
>> checking AUTO_IS_DECLTYPE for a non-auto TEMPLATE_TYPE_PARM.
>>
>>> + && AUTO_IS_DECLTYPE (type))
>>> + {
>>> + error_at (token->location,
>>> + "cannot declare a parameter with %<decltype(auto)%>");
>>> + type = error_mark_node;
>>> + }
>>> if (decl_specs)
>>> {
>>> cp_parser_set_decl_spec_type (decl_specs, type,
>>> diff --git a/gcc/testsuite/g++.dg/pr103497.C b/gcc/testsuite/g++.dg/pr103497.C
>>> new file mode 100644
>>> index 00000000000..bcd421c2907
>>> --- /dev/null
>>> +++ b/gcc/testsuite/g++.dg/pr103497.C
>>> @@ -0,0 +1,7 @@
>>> +// { dg-do compile { target c++14 } }
>>> +
>>> +void foo(decltype(auto)... args); // { dg-error "parameter with .decltype.auto..|no parameter packs" }
>>
>> I noticed for
>>
>> void foo(decltype(auto) arg);
>>
>> we already issue an identical error from grokdeclarator. Perhaps we could
>> instead extend the error handling there to detect decltype(auto)... as well,
>> rather than adding new error handling in cp_parser_simple_type_specifier?
>
> Ah thanks, I didn't notice this; this simplifies the change a fair bit.
> How about this patch instead?
>
> Regtested on x86_64-pc-linux-gnu.
>
> -- 8< --
>
> This patch ensures that checks for usages of 'auto' in function
> parameters also consider parameter packs, since 'type_uses_auto' does
> not seem to consider this case.
>
> PR c++/103497
>
> gcc/cp/ChangeLog:
>
> * decl.cc (grokdeclarator): Check for decltype(auto) in
> parameter pack.
>
> gcc/testsuite/ChangeLog:
>
> * g++.dg/cpp1y/decltype-auto-103497.C: New test.
>
> Signed-off-by: Nathaniel Shead <nathanieloshead@gmail.com>
> ---
> gcc/cp/decl.cc | 3 +++
> gcc/testsuite/g++.dg/cpp1y/decltype-auto-103497.C | 8 ++++++++
> 2 files changed, 11 insertions(+)
> create mode 100644 gcc/testsuite/g++.dg/cpp1y/decltype-auto-103497.C
>
> diff --git a/gcc/cp/decl.cc b/gcc/cp/decl.cc
> index 60f107d50c4..aaf691fce68 100644
> --- a/gcc/cp/decl.cc
> +++ b/gcc/cp/decl.cc
> @@ -14044,6 +14044,9 @@ grokdeclarator (const cp_declarator *declarator,
> error ("cannot use %<::%> in parameter declaration");
>
> tree auto_node = type_uses_auto (type);
> + if (!auto_node && parameter_pack_p)
> + auto_node = type_uses_auto (PACK_EXPANSION_PATTERN (type));
Hmm, I wonder if type_uses_auto should look into PACK_EXPANSION_PATTERN
itself. Would that break anything?
> +
> if (auto_node && !(cxx_dialect >= cxx17 && template_parm_flag))
> {
> if (cxx_dialect >= cxx14)
> diff --git a/gcc/testsuite/g++.dg/cpp1y/decltype-auto-103497.C b/gcc/testsuite/g++.dg/cpp1y/decltype-auto-103497.C
> new file mode 100644
> index 00000000000..cedd661710c
> --- /dev/null
> +++ b/gcc/testsuite/g++.dg/cpp1y/decltype-auto-103497.C
> @@ -0,0 +1,8 @@
> +// PR c++/103497
> +// { dg-do compile { target c++14 } }
> +
> +void foo(decltype(auto)... args); // { dg-error "cannot declare a parameter with .decltype.auto.." }
> +
> +int main() {
> + foo();
> +}
next prev parent reply other threads:[~2023-06-29 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 6:25 Nathaniel Shead
2023-05-27 7:07 ` ping: " Nathaniel Shead
2023-06-13 10:14 ` Nathaniel Shead
2023-06-23 15:59 ` Patrick Palka
2023-06-24 13:24 ` Nathaniel Shead
2023-06-28 17:54 ` Patrick Palka
2023-06-29 17:43 ` Jason Merrill [this message]
2023-06-30 7:05 ` Nathaniel Shead
2023-07-27 3:47 ` 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=5d7ada85-ccaa-bc07-b625-20fdc5dc924c@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathanieloshead@gmail.com \
--cc=ppalka@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).