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/95057] New: missing -Wunused-but-set-variable warning on multiple assignments, not all of them used
Date: Mon, 11 May 2020 12:50:32 +0000	[thread overview]
Message-ID: <bug-95057-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95057

            Bug ID: 95057
           Summary: missing -Wunused-but-set-variable warning on multiple
                    assignments, not all of them used
           Product: gcc
           Version: 10.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: vincent-gcc at vinc17 dot net
  Target Milestone: ---

With -Wunused-but-set-variable, GCC does not warn in the following cases:

int f (int i)
{
  int j;
  j = i + 1;  /* unused */
  j = i + 2;
  return j;
}

int g (int i)
{
  int j, k;
  j = i + 1;
  k = j + 1;
  j = i + 2;  /* unused */
  return k;
}

Note: it is possible that PR44677 may be regarded as a particular case of this
bug.

             reply	other threads:[~2020-05-11 12:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 12:50 vincent-gcc at vinc17 dot net [this message]
2020-05-11 12:53 ` [Bug c/95057] " jakub at gcc dot gnu.org
2020-05-11 13:05 ` vincent-gcc at vinc17 dot net
2020-05-11 13:09 ` jakub at gcc dot gnu.org
2020-05-11 13:39 ` vincent-gcc at vinc17 dot net
2023-07-18 22:34 ` vincent-gcc at vinc17 dot net
2023-07-18 22:46 ` vincent-gcc at vinc17 dot net

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-95057-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).