public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <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:06:24 +0000 [thread overview]
Message-ID: <bug-99677-4-cCFcLcpu0n@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
--- Comment #6 from cqwrteur <unlvsur at live dot com> ---
(In reply to Richard Biener from comment #5)
> I think Andrew is correct. Note we can't elide "unused" not statically
> initialized variables (since the initialization is seen as use).
but here the result is always the same from importing functions from ntdll.dll
or kernel32.dll
next prev parent reply other threads:[~2021-03-22 9:06 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 [this message]
2021-03-22 9:10 ` 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-99677-4-cCFcLcpu0n@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).