public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108299] toplevel thread_local variables are not initialized if not referenced and initialized at wrong moment when referenced Date: Fri, 06 Jan 2023 19:57:35 +0000 [thread overview] Message-ID: <bug-108299-4-TrYkdiNhKI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108299-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108299 Jason Merrill <jason at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-01-06 Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org Keywords| |wrong-code Resolution|INVALID |--- Status|RESOLVED |ASSIGNED Ever confirmed|0 |1 --- Comment #10 from Jason Merrill <jason at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #6) Hmm, I don't see the ABI problem: wrappers are comdat/weak and prepared to handle the absence of an init function, so TUs that either use or don't use wrappers should be ABI-compatible, though of course you would need both to be recompiled to get the currently specified behavior. For performance, the one degradation I see is preventing the PR101786 optimization with extern constinit. https://github.com/cplusplus/CWG/issues/210
next prev parent reply other threads:[~2023-01-06 19:57 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-05 10:51 [Bug c++/108299] New: " agriff at tin dot it 2023-01-05 11:41 ` [Bug c++/108299] " jakub at gcc dot gnu.org 2023-01-05 11:41 ` jakub at gcc dot gnu.org 2023-01-05 14:38 ` agriff at tin dot it 2023-01-05 14:47 ` jakub at gcc dot gnu.org 2023-01-05 14:52 ` agriff at tin dot it 2023-01-05 15:17 ` jakub at gcc dot gnu.org 2023-01-05 15:40 ` redi at gcc dot gnu.org 2023-01-05 15:42 ` redi at gcc dot gnu.org 2023-01-05 15:53 ` agriff at tin dot it 2023-01-06 19:57 ` jason at gcc dot gnu.org [this message] 2023-01-06 20:58 ` jakub 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-108299-4-TrYkdiNhKI@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: linkBe 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).