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

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

--- Comment #4 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
OK, so the work (for this warning or a new one) should be done later, but early
enough not to be affected by optimizations.

One of the goals would be to detect a missing check of a return value of a
function call (typically an error status). For such a typical usage, the same
variable can be reused for each error status.

  int r;

  r = call1 (...);
  check (r);
  /* ... */
  r = call2 (...);
  check (r);
  /* ... */
  r = call3 (...);
  check (r);

If a check is missing, there should be a warning.

  parent reply	other threads:[~2020-05-11 13:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 12:50 [Bug c/95057] New: " vincent-gcc at vinc17 dot net
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 [this message]
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-XcYPg2KVoW@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).