public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/52347] New: -Wno-tabs -Wall -Wno-tabs still warns about tabs Date: Thu, 23 Feb 2012 08:37:00 -0000 [thread overview] Message-ID: <bug-52347-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52347 Bug #: 52347 Summary: -Wno-tabs -Wall -Wno-tabs still warns about tabs Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: burnus@gcc.gnu.org With mosts flags, a flag which is implied by another flag can be overridden by the specific flag. For instance -f(no-)protect-parens overriddes the settings of -O0 (protected) or -Ofast (unprotected parentheses). However, for tab warnings -Wno-tabs cannot be used to turn off the warning, enabled by -Wall. I wouldn't be surprised if that also holds for other warnings, enabled by -Wall or -Wextra. Found at http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/9942915c9c41b151
next reply other threads:[~2012-02-23 8:19 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-23 8:37 burnus at gcc dot gnu.org [this message] 2012-02-23 8:42 ` [Bug fortran/52347] " manu at gcc dot gnu.org 2013-06-14 19:43 ` Simon.Richter at hogyros dot de 2013-06-14 21:27 ` manu at gcc dot gnu.org 2013-06-14 23:15 ` Simon.Richter at hogyros dot de 2013-06-15 9:36 ` manu at gcc dot gnu.org 2014-12-11 17:41 ` burnus at gcc dot gnu.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-52347-4@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: linkBe 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).