public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "trass3r at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94184] Global variable inline constructor elision. Date: Mon, 17 Oct 2022 13:40:22 +0000 [thread overview] Message-ID: <bug-94184-4-VGcfjrLKqh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94184-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94184 Trass3r <trass3r at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trass3r at gmail dot com --- Comment #2 from Trass3r <trass3r at gmail dot com> --- Even simpler example: const struct A { A() {} int a = 0; } a; The global ctor doesn't get eliminated while clang removes it: https://godbolt.org/z/9bjzMbx85 .section .text.startup,"ax",@progbits .type _GLOBAL__sub_I_example.cpp, @function _GLOBAL__sub_I_example.cpp: ret It works if you remove the member a.
next prev parent reply other threads:[~2022-10-17 13:40 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-15 19:36 [Bug c++/94184] New: " maxim.yegorushkin at gmail dot com 2020-03-15 19:52 ` [Bug c++/94184] " pinskia at gcc dot gnu.org 2022-10-17 13:40 ` trass3r at gmail dot com [this message] 2022-10-17 14:11 ` 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-94184-4-VGcfjrLKqh@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).