public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109268] Guard variable still provided for static constinit variable with an empty destructor Date: Sat, 16 Mar 2024 23:18:49 +0000 [thread overview] Message-ID: <bug-109268-4-9kbLSCgOmo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109268-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109268 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2024-03-16 Status|UNCONFIRMED |NEW Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I have a patch which fixes PR 19661 except it does not fix this one fully. I will also note LLVM also still does the guard variable here too even with the removal of the __cxa_atexit call. We need another way to remove the empty code between __cxa_guard_acquire/__cxa_guard_release . <bb 3> [local count: 354334800]: _2 = __cxa_guard_acquire (&_ZGVZ1fvE4data); if (_2 != 0) goto <bb 4>; [33.00%] else goto <bb 5>; [67.00%] <bb 4> [local count: 116930483]: # DEBUG this => &data # DEBUG INLINE_ENTRY __ct data ={v} {CLOBBER(bob)}; # DEBUG this => NULL __cxa_guard_release (&_ZGVZ1fvE4data); <bb 5> [local count: 1073741824]: --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Dup in the end. *** This bug has been marked as a duplicate of bug 84411 ***
prev parent reply other threads:[~2024-03-16 23:18 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-24 0:48 [Bug c++/109268] New: Guard variable still provided for static constinit variable barry.revzin at gmail dot com 2023-03-24 0:50 ` [Bug c++/109268] " pinskia at gcc dot gnu.org 2023-03-24 0:54 ` pinskia at gcc dot gnu.org 2023-03-24 11:54 ` [Bug c++/109268] Guard variable still provided for static constinit variable with an empty destructor jakub at gcc dot gnu.org 2024-03-16 22:37 ` pinskia at gcc dot gnu.org 2024-03-16 23:18 ` pinskia at gcc dot gnu.org [this message]
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-109268-4-9kbLSCgOmo@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).