public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "chengniansun at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/59801] New: GCC does not warn on unused global variable
Date: Tue, 14 Jan 2014 08:26:00 -0000	[thread overview]
Message-ID: <bug-59801-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 59801
           Summary: GCC does not warn on unused global variable
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: chengniansun at gmail dot com

Created attachment 31829
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31829&action=edit
the test case to trigger the bug.

I used the following command 

$gcc -Wall -Wextra -pedantic -std=c11 -c unused-var.c

And GCC outputs no warnings.


However in the source file unused-var.c, the last global variable "g_1853" is
NOT used. 

//////////////////////////////  Start of the source file /////////////
/**
 * compile this program with the following command
 *
 * gcc -c -pedantic -std=c11 -Wall -Wextra unused-var.c
 */


static int g_37 = (-1L);
static int *g_187 = &g_37;

/**
 * this variable will NOT be reported although it is NOT used.
 */
static int ** volatile g_1853 = &g_187;/* VOLATILE GLOBAL g_1853 */

//////////////////////////////  End of the source file /////////////


The Gcc version is 4.9.0, built on 01/09/2014
gcc (GCC) 4.9.0 20140109 (experimental)
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


             reply	other threads:[~2014-01-14  8:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  8:26 chengniansun at gmail dot com [this message]
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
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@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).