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/59801] GCC does not warn on unused global variable
Date: Thu, 16 Jan 2014 08:38:00 -0000	[thread overview]
Message-ID: <bug-59801-4-nZyh4wx4ZE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59801-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59801

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Those two cases are different, the other PR was about automatic volatile
variables, where if they are unused it is really hard to come up with a way how
they could be modified behind compiler's back.  While for this case, variable
in .data/.bss etc. section it is not so hard, the variable has a name through
which it can be referenced, eventhough only from within the same assembly file.
 User could inject some assembly which will access it, the var can use section
attribute that places it into some magic section that is e.g. IO mapped, etc.


  parent reply	other threads:[~2014-01-16  8:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  8:26 [Bug c/59801] New: " chengniansun at gmail dot com
2014-01-14  9:02 ` [Bug c/59801] " jakub at gcc dot gnu.org
2014-01-14 17:32 ` chengniansun at gmail dot com
2014-01-16  6:08 ` su at cs dot ucdavis.edu
2014-01-16  6:33 ` pinskia at gcc dot gnu.org
2014-01-16  6:34 ` pinskia at gcc dot gnu.org
2014-01-16  6:52 ` su at cs dot ucdavis.edu
2014-01-16  8:38 ` jakub at gcc dot gnu.org [this message]
2014-01-16 21:18 ` su at cs dot ucdavis.edu
2014-01-16 21:27 ` 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-59801-4-nZyh4wx4ZE@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).