public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/105210] gcc/auto-profile.cc:391:11: warning: variable 'level' set but not used Date: Sun, 10 Apr 2022 20:04:46 +0000 [thread overview] Message-ID: <bug-105210-4-6Lpjbr7IPS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105210-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105210 --- Comment #1 from David Binderman <dcb314 at hotmail dot com> --- It would appear that clang trunk is better at finding set-but-not-used variables than gcc. Here are some more cases: ./../trunk.git/gcc/genautomata.cc:5664:7: warning: variable 'alts_number' set but not used [-Wunused-but-set-variable] ../../trunk.git/gcc/graphite-poly.cc:344:7: warning: variable 'nb_reads' set but not used [-Wunused-but-set-variable] ../../trunk.git/gcc/graphite-poly.cc:345:7: warning: variable 'nb_writes' set but not used [-Wunused-but-set-variable] ../../trunk.git/gcc/lto-wrapper.cc:1428:12: warning: variable 'n_debugobj' set but not used [-Wunused-but-set-variable] ../../trunk.git/libdecnumber/dpd/decimal64.c:617:8: warning: variable 'n' set but not used [-Wunused-but-set-variable] ../../trunk.git/gcc/tree-switch-conversion.cc:2042:11: warning: variable 'ranges' set but not used [-Wunused-but-set-variable] I am not sure if these variables are candidates for deletion, or some code should be using them.
next prev parent reply other threads:[~2022-04-10 20:04 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-10 19:54 [Bug c/105210] New: " dcb314 at hotmail dot com 2022-04-10 20:04 ` dcb314 at hotmail dot com [this message] 2022-04-10 20:12 ` [Bug c/105210] " dcb314 at hotmail dot com 2022-04-10 21:58 ` [Bug gcov-profile/105210] " pinskia at gcc dot gnu.org 2022-04-10 22:10 ` egallager at gcc dot gnu.org 2022-04-10 22:29 ` pinskia at gcc dot gnu.org 2022-04-11 8:13 ` marxin at gcc dot gnu.org 2022-04-11 14:24 ` marxin at gcc dot gnu.org 2022-04-12 17:56 ` dcb314 at hotmail dot com 2022-04-12 18:45 ` marxin at gcc dot gnu.org 2022-05-05 13:05 ` marxin at gcc dot gnu.org 2022-05-05 15:43 ` dcb314 at hotmail dot com 2022-05-05 18:31 ` marxin 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-105210-4-6Lpjbr7IPS@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).