public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/52106] New: missing -Wunused-but-set-variable warning with the a = b = ... construct
Date: Fri, 03 Feb 2012 12:34:00 -0000	[thread overview]
Message-ID: <bug-52106-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 52106
           Summary: missing -Wunused-but-set-variable warning with the a =
                    b = ... construct
    Classification: Unclassified
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: vincent-gcc@vinc17.net


The following code

int foo (void)
{
  int a, b, c, d;
  a = b = 0;
  c = d = 0;
  return a + d;
}

gives:

$ gcc-snapshot -Wall -c tst.c
tst.c: In function 'foo':
tst.c:3:13: warning: variable 'c' set but not used [-Wunused-but-set-variable]

One would expect the same warning for variable 'b'. Even though it appears to
be used to assign variable 'a', it shouldn't count in such a construct. Indeed
a variable assignment is useless if the variable isn't used in a later
expression (if the goal is to convert the value, then a cast would be more
readable).

Tested with:
gcc (Debian 20120128-1) 4.7.0 20120128 (experimental) [trunk revision 183664]


             reply	other threads:[~2012-02-03 12:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 12:34 vincent-gcc at vinc17 dot net [this message]
2012-02-03 12:54 ` [Bug c/52106] " jakub at gcc dot gnu.org
2012-02-03 13:29 ` [Bug c/52106] warning for useless assignments vincent-gcc at vinc17 dot net
2012-02-03 13:33 ` rguenth at gcc dot gnu.org
2012-02-03 17:18 ` [Bug c/52106] [C11] missing -Wunused-but-set-variable warning with the a = b = ... construct pinskia 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-52106-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).