public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/105210] gcc/auto-profile.cc:391:11: warning: variable 'level' set but not used
Date: Sun, 10 Apr 2022 22:10:08 +0000 [thread overview]
Message-ID: <bug-105210-4-lPHWnZa5My@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
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=44677
Keywords| |diagnostic
CC| |egallager at gcc dot gnu.org
Blocks| |89180
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> (In reply to David Binderman from comment #2)
> > It seems that recent gcc trunk can't detect set-but-not-used in this code:
>
> There is another bug about this already but I can't find that one right now
bug 44677?
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89180
[Bug 89180] [meta-bug] bogus/missing -Wunused warnings
next prev parent reply other threads:[~2022-04-10 22:10 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 ` [Bug c/105210] " dcb314 at hotmail dot com
2022-04-10 20:12 ` 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 [this message]
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-lPHWnZa5My@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).