public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Patrick Palka <ppalka@redhat.com>, gcc-patches@gcc.gnu.org
Cc: nathanieloshead@gmail.com
Subject: Re: [PATCH] c++/modules: deduced return type merging [PR114795]
Date: Tue, 23 Apr 2024 13:29:04 -0400	[thread overview]
Message-ID: <468ca4fe-710f-4524-a976-9774a0452817@redhat.com> (raw)
In-Reply-To: <20240423164101.3016046-1-ppalka@redhat.com>

On 4/23/24 09:41, Patrick Palka wrote:
> Tested on x86_64-pc-linux-gnu, does this look OK for trunk?
> 
> -- >8 --
> 
> When merging an imported function template specialization with an
> existing one, if the existing one has an undeduced return type and the
> imported one's is already deduced, we need to propagate the deduced type
> since once we install the imported definition we won't get a chance to
> deduce it by normal means.
> 
> This patch makes is_matching_decl propagate the deduced return type
> alongside the existing propagate of the existing specification.  I
> suppose could instead propagate it later when installing the imported
> definition from read_definition, but it seems best to propagate it
> sooner rather than later.
> 
> 	PR c++/114795
> 
> gcc/cp/ChangeLog:
> 
> 	* module.cc (trees_in::is_matching_decl): Propagate deduced
> 	function return type.
> 
> gcc/testsuite/ChangeLog:
> 
> 	* g++.dg/modules/auto-4_a.H: New test.
> 	* g++.dg/modules/auto-4_b.C: New test.
> ---
>   gcc/cp/module.cc                        |  5 +++++
>   gcc/testsuite/g++.dg/modules/auto-4_a.H | 14 ++++++++++++++
>   gcc/testsuite/g++.dg/modules/auto-4_b.C | 15 +++++++++++++++
>   3 files changed, 34 insertions(+)
>   create mode 100644 gcc/testsuite/g++.dg/modules/auto-4_a.H
>   create mode 100644 gcc/testsuite/g++.dg/modules/auto-4_b.C
> 
> diff --git a/gcc/cp/module.cc b/gcc/cp/module.cc
> index d94d8ff4df9..e10e19ac9f7 100644
> --- a/gcc/cp/module.cc
> +++ b/gcc/cp/module.cc
> @@ -11537,6 +11537,11 @@ trees_in::is_matching_decl (tree existing, tree decl, bool is_typedef)
>         else if (!DEFERRED_NOEXCEPT_SPEC_P (d_spec)
>   	       && !comp_except_specs (d_spec, e_spec, ce_type))
>   	goto mismatch;
> +
> +      /* Similarly if EXISTING has an undeduced return type, but DECL's
> +	 is already deduced.  */
> +      if (undeduced_auto_decl (existing) && !undeduced_auto_decl (decl))
> +	TREE_TYPE (existing) = change_return_type (TREE_TYPE (d_type), e_type);

Perhaps this should dump a note like the noexcept merge does?  OK either 
way.

Jason


      parent reply	other threads:[~2024-04-23 17:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 16:41 Patrick Palka
2024-04-23 16:45 ` Patrick Palka
2024-04-23 17:29 ` 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=468ca4fe-710f-4524-a976-9774a0452817@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).