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++/106009] [modules] internal compiler error: in import_entity_index with templated local enum in header unit
Date: Fri, 01 Mar 2024 22:24:38 +0000	[thread overview]
Message-ID: <bug-106009-4-Zp8XMafnk6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106009-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106009

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:574fd1f17f100c7c355ad26bc525ab5a3386bb2d

commit r14-9268-g574fd1f17f100c7c355ad26bc525ab5a3386bb2d
Author: Patrick Palka <ppalka@redhat.com>
Date:   Fri Mar 1 17:24:15 2024 -0500

    c++/modules: depending local enums [PR104919, PR106009]

    For local enums defined in a non-template function or a function template
    instantiation it seems we neglect to make the function depend on the enum
    definition (which modules considers logically separate), which ultimately
    causes the enum definition to not be properly streamed before uses
    within the function definition are streamed.

    The code responsible for noting such dependencies is

    gcc/cp/module.cc
    @@ -8784,17 +8784,6 @@ trees_out::decl_node (tree decl, walk_kind ref)
       depset *dep = NULL;
       if (streaming_p ())
         dep = dep_hash->find_dependency (decl);
    !  else if (TREE_CODE (ctx) != FUNCTION_DECL
    !          || TREE_CODE (decl) == TEMPLATE_DECL
    !          || (dep_hash->sneakoscope && DECL_IMPLICIT_TYPEDEF_P (decl))
    !          || (DECL_LANG_SPECIFIC (decl)
    !              && DECL_MODULE_IMPORT_P (decl)))
    !    {
    !      auto kind = (TREE_CODE (decl) == NAMESPACE_DECL
    !                  && !DECL_NAMESPACE_ALIAS (decl)
    !                  ? depset::EK_NAMESPACE : depset::EK_DECL);
    !      dep = dep_hash->add_dependency (decl, kind);
    !    }

       if (!dep)
         {

    and the condition there notably excludes local TYPE_DECLs from a
    non-template-pattern function (when streaming a template pattern
    we'll see be dealing with the corresponding TEMPLATE_DECL of the
    local TYPE_DECL here, so we'll add the dependency).

    Local classes on the other hand seem to work properly, but perhaps by
    accident: with a local class we end up making the function depend on the
    injected-class-name of the local class rather than the local class as a
    whole because the injected-class-name satisfies the criteria (since its
    context is the local class, not the function).

    The 'sneakoscope' flag is set when walking a function declaration and
    its purpose seems to be to catch a local type that escapes the function
    via a deduced return type (so called voldemort types) and note a
    dependency on them.  But there seems to be no reason to restrict this
    behavior to voldemort types, and indeed consistently noting the dependency
    for all local types fixes these PRs (almost).  So this patch gets rid of
    this flag and enables the dependency tracking unconditionally.

    This was nearly enough to make things work, except we now ran into
    issues with the local TYPE_/CONST_DECL copies from the pre-gimplified
    version of a constexpr function body during streaming.  Rather than
    making modules cope with this, it occurred to me that we don't need to
    make copies of local types when saving the pre-gimplified body (and when
    making further copies thereof); only VAR_DECLs etc need to be copied
    (so that we don't conflate local variables from different recursive
    calls to the same function during constexpr evaluation).  So this patch
    adjusts copy_fn accordingly.

            PR c++/104919
            PR c++/106009

    gcc/cp/ChangeLog:

            * module.cc (depset::hash::sneakoscope): Remove.
            (trees_out::decl_node): Always add a dependency on a local type.
            (depset::hash::find_dependencies): Remove sneakoscope stuff.

    gcc/ChangeLog:

            * tree-inline.cc (remap_decl): Handle copy_decl returning the
            original decl.
            (remap_decls): Handle remap_decl returning the original decl.
            (copy_fn): Adjust copy_decl callback to skip TYPE_DECL and
            CONST_DECL.

    gcc/testsuite/ChangeLog:

            * g++.dg/modules/tdef-7.h: Remove outdated comment.
            * g++.dg/modules/tdef-7_b.C: Don't expect two TYPE_DECLs.
            * g++.dg/modules/enum-13_a.C: New test.
            * g++.dg/modules/enum-13_b.C: New test.

  parent reply	other threads:[~2024-03-01 22:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  3:12 [Bug c++/106009] New: [modules] internal compiler error: in mark_by_value, at cp/module.cc:4775 overlord624 at gmail dot com
2022-06-17  3:14 ` [Bug c++/106009] " overlord624 at gmail dot com
2022-10-18  0:33 ` [Bug c++/106009] [modules] internal compiler error: in import_entity_index with templated local enum in header unit ppalka at gcc dot gnu.org
2024-02-13 19:01 ` ppalka at gcc dot gnu.org
2024-02-29 18:04 ` ppalka at gcc dot gnu.org
2024-03-01 22:24 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-01 22:26 ` ppalka 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-106009-4-Zp8XMafnk6@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: 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).