This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Patch to move warning for X<=Y<=Z from -W to -Wparentheses
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: "Joseph S. Myers" <jsm at polyomino dot org dot uk>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Fri, 6 Aug 2004 09:46:22 +0200 (CEST)
- Subject: Re: Patch to move warning for X<=Y<=Z from -W to -Wparentheses
- References: <Pine.LNX.4.58.0407161601180.29102@digraph.polyomino.org.uk><Pine.LNX.4.58.0407191928020.4987@linux.site><Pine.LNX.4.58.0407202202010.19920@digraph.polyomino.org.uk>
On Tue, 20 Jul 2004, Joseph S. Myers wrote:
This patch moves the warning about comparisons such as X<=Y<=Z from
-Wextra into -Wparentheses.
Would you mind adding a short note to gcc-3.5/changes.html?
I'm still unconvinced that such trivial tweaks to which warnings on in
what option deserve mention in the release notes (cf.
<http://gcc.gnu.org/ml/gcc-patches/2003-11/msg00816.html>); though in this
case there was no bug report requesting the move, if anything that makes
it less significant and less worthy of comment.
My reasoning was/is that users may need to adjust their Makefiles to get
the original behavior they may have come to rely upon.
But perhaps you have specific criteria in mind for what changes merit
(a) mention on release notes, (b) mention on the front page of
gcc.gnu.org, (c) mention on gcc-announce.
In my opinion, everything that requires a user to edit a Makefile or
source code is a good candidate for being mentioned in the release notes.
Larger accomplishments, either as part of a specific, focused project, or
long term committment, merit mention on the front page. Examples include
things like tree-ssa, new backends, major advances in optimization or
standards compliance
gcc-announce for new releases and announcements of frontends or backends
being dropped, for example.
Gerald