From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29322 invoked by alias); 23 Feb 2012 08:37:41 -0000 Received: (qmail 29252 invoked by uid 22791); 23 Feb 2012 08:37:40 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 23 Feb 2012 08:37:28 +0000 From: "manu at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/52347] -Wno-tabs -Wall -Wno-tabs still warns about tabs Date: Thu, 23 Feb 2012 08:42:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: manu 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-Changed-Fields: CC Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-02/txt/msg02282.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D52347 Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manu at gcc dot gnu.org --- Comment #1 from Manuel L=C3=B3pez-Ib=C3=A1=C3=B1ez 2012-02-23 08:37:08 UTC --- (In reply to comment #0) > However, for tab warnings -Wno-tabs cannot be used to turn off the warnin= g, > enabled by -Wall. >=20 > I wouldn't be surprised if that also holds for other warnings, enabled by= -Wall > or -Wextra. >=20 > Found at > http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/994= 2915c9c41b151 Sure, it happens with many flags in fact, not only in Fortran, since -Wall either does not check whether the flag was already initialized, or it sets = the value too early. Ideally, flags that enable other flags should be checked l= ast, and they should only touch flags that haven't been set already in the command-line. But this is only done on a case-by-case basis by using -1 as starting value (I did it mostly for -Wextra, -Wunused, and -Wimplicit). It would be nice that the options handling code would take care of this, by specifying the relations in *.opt files.