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: Tue, 18 Jul 2023 22:34:22 +0000 [thread overview] Message-ID: <bug-95057-4-1a0jfgxpVs@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 #5 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> --- FYI, Clang 16 does not warn either on the testcases provided in comment 0 (bug report). But contrary to GCC (tested with master r14-1713-g6631fe419c6 - Debian gcc-snapshot package 20230613-1), Clang 15 and 16 both warn on f and g below: int h (void); void f (void) { int i = h (); i++; } void g (void) { for (int i = 0 ;; i++) if (h ()) break; } zira:~> clang-15 -c -Wunused-but-set-variable warn-inc.c warn-inc.c:5:7: warning: variable 'i' set but not used [-Wunused-but-set-variable] int i = h (); ^ warn-inc.c:11:12: warning: variable 'i' set but not used [-Wunused-but-set-variable] for (int i = 0 ;; i++) ^ 2 warnings generated. Thanks to this detection, a test with Clang 16 found two issues in GNU MPFR (one cosmetic about a useless loop variable and one important in the testsuite). So it is useful to consider such particular cases.
next prev parent reply other threads:[~2023-07-18 22:34 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 2023-07-18 22:34 ` vincent-gcc at vinc17 dot net [this message] 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-1a0jfgxpVs@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: linkBe 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).