public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/13029] [3.4 Regression] static consts and -Wunused-variable
Date: Mon, 17 Feb 2014 08:18:00 -0000 [thread overview]
Message-ID: <bug-13029-4-CiAuuwtTY3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-13029-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13029
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Well, clang strategy seems to be not to bother with false positives and always
prefer warning over not warning on anything, so usually the clang output is
just completely unreadable because among the tons of false positives it is hard
to find actual real code problems. GCC strategy is to find some ballance
between false positive warnings and missed warnings.
next prev parent reply other threads:[~2014-02-17 8:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-13029-4@http.gcc.gnu.org/bugzilla/>
2014-02-17 8:10 ` chengniansun at gmail dot com
2014-02-17 8:18 ` jakub at gcc dot gnu.org [this message]
2014-02-17 8:41 ` mikpelinux at gmail dot com
2014-02-17 9:07 ` chengniansun at gmail dot com
2014-02-17 9:12 ` jakub at gcc dot gnu.org
2014-02-17 21:14 ` tromey at gcc dot gnu.org
2003-11-12 21:58 [Bug c/13029] New: " mrs at apple dot com
2003-11-12 22:10 ` [Bug c/13029] [3.4 Regression] " pinskia at gcc dot gnu dot org
2003-11-13 19:40 ` cvs-commit at gcc dot gnu dot org
2003-11-13 19:42 ` mmitchel at gcc dot gnu dot 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-13029-4-CiAuuwtTY3@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).