public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@acm.org>
To: Patrick Palka <ppalka@redhat.com>
Cc: gcc-patches@gcc.gnu.org, jason@redhat.com
Subject: Re: [PATCH] c++ modules: lazy loading from within template [PR99377]
Date: Tue, 11 Oct 2022 13:12:38 -0400	[thread overview]
Message-ID: <13ac0eb2-6527-057f-4b4a-8514542a9350@acm.org> (raw)
In-Reply-To: <d024ad1e-e542-25f1-b39b-324ea846a67d@idea>

On 10/11/22 10:58, Patrick Palka wrote:
> On Mon, 10 Oct 2022, Nathan Sidwell wrote:
> 
>> On 10/4/22 13:36, Patrick Palka wrote:
>>> Here when lazily loading the binding for f at parse time from the
>>> template g, processing_template_decl is set and thus the call to
>>> note_vague_linkage_fn from module_state::read_cluster has no effect,
>>> and we never push f onto deferred_fns and end up never emitting its
>>> definition.
>>>
>>> ISTM the behavior of the lazy loading machinery shouldn't be sensitive
>>> to whether we're inside a template, and therefore we should probably be
>>> clearing processing_template_decl somewhere e.g in lazy_load_binding.
>>> This is sufficient to fix the testcase.
>>
>> yeah, I remember hitting issues with this, but thought I'd got rid of the need
>> to override processing_template_decl.  Do you also need to override it in
>> lazy_load_pendings though? that's a lazy loader and my suspicion is it might
>> be susceptible to the same issues.
> 
> Hmm yeah, looks like we need to override it in lazy_load_pendings too:
> I ran the testsuite with gcc_assert (!processing_template_decl) added to
> module_state::read_cluster and if we don't also override it in
> lazy_load_binding then the assert triggers for pr99425-2_b.X.
> 
>>
>>>
>>> But it also seems the processing_template_decl test in
>>> note_vague_linkage_fn, added by r8-7539-g977bc3ee11383e for PR84973, is
>>> perhaps too strong: if the intent is to avoid deferring output for
>>> uninstantiated templates, we should make sure that DECL in question is
>>> an uninstantiated template by checking e.g. value_dependent_expression_p.
>>> This too is sufficient to fix the testcase (since f isn't a template)
>>> and survives bootstrap and regtest.
>>
>> I think this is an orthogonal issue -- can we remove it from this patch?
> 
> Done.
> 
> -- >8 --
> 
> Subject: [PATCH] c++ modules: lazy loading from within template [PR99377]
> 
> Here when lazily loading the binding for f at parse time from the
> template g, processing_template_decl is set and thus the call to
> note_vague_linkage_fn from module_state::read_cluster has no effect,
> and we never push f onto deferred_fns and end up never emitting its
> definition.
> 
> ISTM the behavior of the lazy loading machinery shouldn't be sensitive
> to whether we're inside a template, and therefore we should be clearing
> processing_template_decl in the entrypoints lazy_load_binding and
> lazy_load_pendings.
> 
> 	PR c++/99377
> 
> gcc/cp/ChangeLog:
> 
> 	* module.cc (lazy_load_binding): Clear processing_template_decl.
> 	(lazy_load_pendings): Likewise.

ok, thanks

> 
> gcc/testsuite/ChangeLog:
> 
> 	* g++.dg/modules/pr99377-2_a.C: New test.
> 	* g++.dg/modules/pr99377-2_b.C: New test.
> ---
>   gcc/cp/module.cc                           | 8 ++++++++
>   gcc/testsuite/g++.dg/modules/pr99377-2_a.C | 5 +++++
>   gcc/testsuite/g++.dg/modules/pr99377-2_b.C | 6 ++++++
>   3 files changed, 19 insertions(+)
>   create mode 100644 gcc/testsuite/g++.dg/modules/pr99377-2_a.C
>   create mode 100644 gcc/testsuite/g++.dg/modules/pr99377-2_b.C
> 
> diff --git a/gcc/cp/module.cc b/gcc/cp/module.cc
> index 94fbee85225..7c48602136c 100644
> --- a/gcc/cp/module.cc
> +++ b/gcc/cp/module.cc
> @@ -19081,6 +19081,10 @@ lazy_load_binding (unsigned mod, tree ns, tree id, binding_slot *mslot)
>   
>     timevar_start (TV_MODULE_IMPORT);
>   
> +  /* Make sure lazy loading from a template context behaves as if
> +     from a non-template context.  */
> +  processing_template_decl_sentinel ptds;
> +
>     /* Stop GC happening, even in outermost loads (because our caller
>        could well be building up a lookup set).  */
>     function_depth++;
> @@ -19129,6 +19133,10 @@ lazy_load_binding (unsigned mod, tree ns, tree id, binding_slot *mslot)
>   void
>   lazy_load_pendings (tree decl)
>   {
> +  /* Make sure lazy loading from a template context behaves as if
> +     from a non-template context.  */
> +  processing_template_decl_sentinel ptds;
> +
>     tree key_decl;
>     pending_key key;
>     key.ns = find_pending_key (decl, &key_decl);
> diff --git a/gcc/testsuite/g++.dg/modules/pr99377-2_a.C b/gcc/testsuite/g++.dg/modules/pr99377-2_a.C
> new file mode 100644
> index 00000000000..26e2bccbbbe
> --- /dev/null
> +++ b/gcc/testsuite/g++.dg/modules/pr99377-2_a.C
> @@ -0,0 +1,5 @@
> +// PR c++/99377
> +// { dg-additional-options -fmodules-ts }
> +// { dg-module-cmi pr99377 }
> +export module pr99377;
> +export inline void f() { }
> diff --git a/gcc/testsuite/g++.dg/modules/pr99377-2_b.C b/gcc/testsuite/g++.dg/modules/pr99377-2_b.C
> new file mode 100644
> index 00000000000..69571952c8a
> --- /dev/null
> +++ b/gcc/testsuite/g++.dg/modules/pr99377-2_b.C
> @@ -0,0 +1,6 @@
> +// PR c++/99377
> +// { dg-additional-options -fmodules-ts }
> +// { dg-do link }
> +import pr99377;
> +template<class> void g() { f(); }
> +int main() { g<int>(); }

-- 
Nathan Sidwell


      reply	other threads:[~2022-10-11 17:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 17:36 Patrick Palka
2022-10-05 12:55 ` Patrick Palka
2022-10-10 21:01 ` Nathan Sidwell
2022-10-11 14:58   ` Patrick Palka
2022-10-11 17:12     ` Nathan Sidwell [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=13ac0eb2-6527-057f-4b4a-8514542a9350@acm.org \
    --to=nathan@acm.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.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).