public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nshead at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/114685] [modules] ICE when exporting a type through a different alias then one declared in GMF
Date: Thu, 11 Apr 2024 13:49:32 +0000	[thread overview]
Message-ID: <bug-114685-4-xmo1n7sxtz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114685-4@http.gcc.gnu.org/bugzilla/>

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

Nathaniel Shead <nshead at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=114683
             Status|UNCONFIRMED                 |NEW
                 CC|                            |nshead at gcc dot gnu.org
   Last reconfirmed|                            |2024-04-11
     Ever confirmed|0                           |1

--- Comment #2 from Nathaniel Shead <nshead at gcc dot gnu.org> ---
This fails on

      if (data->hash->add_namespace_entities (decl, data->partitions))
        {
          /* It contains an exported thing, so it is exported.  */
          gcc_checking_assert (DECL_MODULE_PURVIEW_P (decl));
          DECL_MODULE_EXPORT_P (decl) = true;
        }

ultimately for a very similar reason to PR114683: non-functions brought in by
using-decls currently just bind the value directly which means that there's
nothing to indicate that they should be exported from this scope (and not their
original one).

I've been playing around with making use of the existing STAT_HACK machinery to
try to get this working, but it looks like we'll probably need to overhaul a
fair chunk of the name lookup code to handle this correctly.

  parent reply	other threads:[~2024-04-11 13:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 20:51 [Bug c++/114685] New: " m.cencora at gmail dot com
2024-04-10 21:11 ` [Bug c++/114685] " m.cencora at gmail dot com
2024-04-11 13:49 ` nshead at gcc dot gnu.org [this message]
2024-04-24 13:53 ` ppalka at gcc dot gnu.org
2024-04-26 20:55 ` m.cencora at gmail dot com

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-114685-4-xmo1n7sxtz@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).