public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/53313] Add warning levels
Date: Wed, 22 Apr 2015 16:13:00 -0000 [thread overview]
Message-ID: <bug-53313-4-APz3uvMS53@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53313-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53313
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |easyhack
--- Comment #7 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
It doesn't make sense to really enable every -Wx option, some of them are too
specialized (-Wdouble-promotion, -Wtraditional, -Wlarger-than=, -Wc++-compat,
etc.)
However, if someone goes through the trouble of compiling a list of potential
candidates, it should be trivial to implement using EnabledBy() in common.opt,
c.opt, etc.
Now I think the original proposal of having warnings levels is not what GCC
wants. In fact, we now have -Ofast, -Os, and -Og and the consensus seems to be
that we do not want to have -O4. According to
https://gcc.gnu.org/wiki/DiagnosticsGuidelines
<quote>
* enabled by default if it has (almost) no false positives (e.g., -Woverflow);
* added to -Wall if it is generally useful with low number of false positives
that are easy to work-around;
* added to -Wextra if it has quite a lot of false positives but they are still
easy to work-around;
Warning options should move up in this list when bugfixes reduce the number of
false positives. These cases are not meant to be exhaustive: some options
should never be enabled by other option if the warning is too specific
(-Wdouble-promotion); other options are already controlled by options such as
-Wpedantic and -Wformat and do not need to move up in this list (but they might
if deemed useful).
</quote>
We could add:
* always added to -Weverything unless the warning was never meant to be
generally useful even if it were perfect (-Wdouble-promotion, -Wtraditional,
-Wlarger-than=, -Wc++-compat, etc.).
>From gcc-bugs-return-484364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 22 16:15:26 2015
Return-Path: <gcc-bugs-return-484364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11088 invoked by alias); 22 Apr 2015 16:15:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11049 invoked by uid 55); 22 Apr 2015 16:15:22 -0000
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65296] [avr] fix various issues with specs file generation
Date: Wed, 22 Apr 2015 16:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gjl at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: gjl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65296-4-3yNoi5tqu4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65296-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65296-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-04/txt/msg01916.txt.bz2
Content-length: 842
https://gcc.gnu.org/bugzilla/show_bug.cgi?ide296
--- Comment #10 from Georg-Johann Lay <gjl at gcc dot gnu.org> ---
Author: gjl
Date: Wed Apr 22 16:14:50 2015
New Revision: 222333
URL: https://gcc.gnu.org/viewcvs?rev"2333&root=gcc&view=rev
Log:
Backport from trunk r222179.
2015-04-17 Sivanupandi Pitchumani <Pitchumani.Sivanupandi@atmel.com>
PR target/65296
* config/avr/gen-avr-mmcu-specs.c (*avrlibc_startfile): Adjust
to new AVR-LibC file layout (bug #44574).
(*avrlibc_devicelib): Same.
* config/avr/avr-mcus.def: Adjust comments.
* config/avr/avr.opt (nodevicelib): Adjust help.
Modified:
branches/gcc-5-branch/gcc/ChangeLog
branches/gcc-5-branch/gcc/config/avr/avr-mcus.def
branches/gcc-5-branch/gcc/config/avr/avr.opt
branches/gcc-5-branch/gcc/config/avr/gen-avr-mmcu-specs.c
next prev parent reply other threads:[~2015-04-22 16:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 22:00 [Bug other/53313] New: " DeusExSophismata at gmail dot com
2012-05-10 22:04 ` [Bug other/53313] " DeusExSophismata at gmail dot com
2012-08-16 3:49 ` david at doublewise dot net
2012-09-30 7:24 ` jan.kratochvil at redhat dot com
2012-09-30 13:16 ` manu at gcc dot gnu.org
2012-12-08 17:59 ` glisse at gcc dot gnu.org
2014-03-17 10:37 ` slyfox at inbox dot ru
2015-04-22 16:13 ` manu at gcc dot gnu.org [this message]
2015-04-24 1:16 ` david at doublewise dot net
2015-04-24 10:29 ` manu at gcc dot gnu.org
2015-04-24 11:59 ` glisse at gcc dot gnu.org
2015-04-24 13:53 ` david at doublewise dot net
2015-04-24 14:22 ` redi at gcc dot gnu.org
2015-04-25 15:10 ` david at doublewise 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-53313-4-APz3uvMS53@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).