public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "guojiufu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105322] [modules] ICE with constexpr object of local class type from another function
Date: Thu, 28 Apr 2022 03:54:21 +0000	[thread overview]
Message-ID: <bug-105322-4-IUpxK3MgfX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105322-4@http.gcc.gnu.org/bugzilla/>

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

Jiu Fu Guo <guojiufu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |guojiufu at gcc dot gnu.org

--- Comment #3 from Jiu Fu Guo <guojiufu at gcc dot gnu.org> ---
One finding:
In trees_out::decl_node, there are code lines:

    case FIELD_DECL:
      {
        if (streaming_p ())
          i (tt_data_member);

        tree ctx = DECL_CONTEXT (decl);
        tree_node (ctx); //The context, is the struct "S" inside foo, "S" is
handled in 'tree_node', and "insert" is called for member "d".

        tree name = NULL_TREE;

        if (TREE_CODE (decl) == USING_DECL)
          ;
        else
          {
            name = DECL_NAME (decl);
            if (name && IDENTIFIER_ANON_P (name))
              name = NULL_TREE;
          }

        tree_node (name);
        if (!name && streaming_p ())
          {
            unsigned ix = get_field_ident (ctx, decl);
            u (ix);
          }

        int tag = insert (decl); //HERE, "insert" is called again member "d". 

It may be a direct cause that "insert" is called twice for "d", and then a
crash occurs.

While I do not know much about the code and do not found a fix.

  parent reply	other threads:[~2022-04-28  3:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20 20:08 [Bug c++/105322] New: " ppalka at gcc dot gnu.org
2022-04-20 20:11 ` [Bug c++/105322] " ppalka at gcc dot gnu.org
2022-04-21 12:35 ` cvs-commit at gcc dot gnu.org
2022-04-28  3:54 ` guojiufu at gcc dot gnu.org [this message]
2022-10-21 19:37 ` ppalka at gcc dot gnu.org
2023-04-26  6:55 ` rguenth at gcc dot gnu.org
2023-07-27  9:22 ` rguenth at gcc dot gnu.org
2023-10-20 20:25 ` cvs-commit at gcc dot gnu.org
2023-10-24  0:47 ` ppalka at gcc dot gnu.org
2023-10-24  0:47 ` 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-105322-4-IUpxK3MgfX@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).