public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nov.ondrej at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113292] New: [modules] internal error when compiling header to module containing static thread_local variable
Date: Tue, 09 Jan 2024 16:14:57 +0000	[thread overview]
Message-ID: <bug-113292-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113292
           Summary: [modules] internal error when compiling header to
                    module containing static thread_local variable
           Product: gcc
           Version: 13.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: nov.ondrej at gmail dot com
  Target Milestone: ---

may be similar to #99187

you can also see here : https://godbolt.org/z/o4Kf8ed85

class test {
    static const test &get_instance() {
        return instance;
    }
    static thread_local test instance;
};


Compile with :-std=c++20 -fmodules-ts -x c++-header

internal compiler error: in tree_node, at cp/module.cc:9264
0x263852c internal_error(char const*, ...)
        ???:0
0xa4edb5 fancy_abort(char const*, int, char const*)
        ???:0
0xbbf621 trees_out::core_vals(tree_node*)
        ???:0
0xbc1ef8 trees_out::tree_value(tree_node*)
        ???:0
0xbbea88 trees_out::tree_node(tree_node*)
        ???:0
...



The error appears, when function is reading static thread_local variable

Ondrej

             reply	other threads:[~2024-01-09 16:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-09 16:14 nov.ondrej at gmail dot com [this message]
2024-01-16 22:41 ` [Bug c++/113292] " cvs-commit at gcc dot gnu.org
2024-01-27 10:32 ` nshead 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-113292-4@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).