From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-484555-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 5893 invoked by alias); 24 Apr 2015 11:59:44 -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
Received: (qmail 5822 invoked by uid 48); 24 Apr 2015 11:59:39 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/53313] Add warning levels
Date: Fri, 24 Apr 2015 11:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: easyhack
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-53313-4-FE8D3PETnx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-53313-4@http.gcc.gnu.org/bugzilla/>
References: <bug-53313-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/msg02107.txt.bz2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53313

--- Comment #10 from Marc Glisse <glisse at gcc dot gnu.org> ---
Manuel, you seem to want a -Wsuper-extra that you can use everyday (maybe with
a couple -Wno-*). What some other people want with -Weverything is a way to
discover what warnings are available in the compiler. For instance, they
discover a bug or a performance issue in their code, extract a small
reproducer, and want to find if there exists a flag that would help them narrow
down the places they need to review in the rest of their code base for similar
issues. So yes, it should warn all over the place and give contradictory
advice, it should even include the warning that just tells you how large your
function is. As a bonus, this makes it obvious to users that they are not
supposed to make their code -Weverything clean. Maybe the name -Wrant would
make it more acceptable?