public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99677] [[gnu::const]] attribute does not prevent dead global variable gets emitted. Date: Mon, 22 Mar 2021 09:10:38 +0000 [thread overview] Message-ID: <bug-99677-4-KfAx9Tttpo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99677-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99677 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org, | |jason at gcc dot gnu.org --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- As the functions aren't constexpr, they aren't even considered during C++ FE constexpr processing. gnu::const means something completely different. I bet we optimize away static const variables only written (even with non-constant initializers) and never address taken or otherwise used, this PR seems to ask to handle inline const (with the C++ FE specific behavior for them) in such cases too. I'm not sure it is valid if the vars are odr-used somewhere and the odr-uses are later optimized away, I think emitting the inline vars in that case is part of the ABI. And the not odr-used cases which are only used by their initialization is yet another question.
prev parent reply other threads:[~2021-03-22 9:10 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-20 3:24 [Bug c++/99677] New: " unlvsur at live dot com 2021-03-20 3:41 ` [Bug c++/99677] " unlvsur at live dot com 2021-03-20 3:46 ` unlvsur at live dot com 2021-03-20 3:53 ` pinskia at gcc dot gnu.org 2021-03-20 6:13 ` unlvsur at live dot com 2021-03-22 8:57 ` rguenth at gcc dot gnu.org 2021-03-22 9:06 ` unlvsur at live dot com 2021-03-22 9:10 ` jakub 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-99677-4-KfAx9Tttpo@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).