public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/58001] Make it possible to silence "Extension: Tab character in format" warning Date: Tue, 30 Jul 2013 12:59:00 -0000 [thread overview] Message-ID: <bug-58001-4-dtyP9g3Cby@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58001-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58001 Dominique d'Humieres <dominiq at lps dot ens.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2013-07-30 Ever confirmed|0 |1 --- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- Compiling the following code with -Wtabs print *, "A string with Tabs instead of spaces" print 1894 1894 format( '123') end gives pr58001.f90:3.14: 1894 format( '123') 1 Warning: Extension: Tab character in format at (1) If compiled with -Wno-tabs, it gives pr58001.f90:2.1: print 1894 1 Warning: Nonconforming tab character at (1) pr58001.f90:3.14: 1894 format( '123') 1 Warning: Nonconforming tab character at (1) pr58001.f90:3.14: 1894 format( '123') 1 Warning: Extension: Tab character in format at (1) Is this the expected behavior?-(I was expecting the later output for -Wtabs, and no warning with -Wno-tabs: on most options Wno-* suppress the warnings for the corresponding option.)
next prev parent reply other threads:[~2013-07-30 12:59 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-27 10:36 [Bug fortran/58001] New: " burnus at gcc dot gnu.org 2013-07-27 14:55 ` [Bug fortran/58001] " kargl at gcc dot gnu.org 2013-07-30 12:59 ` dominiq at lps dot ens.fr [this message] 2013-07-30 17:42 ` sgk at troutmask dot apl.washington.edu 2013-07-30 17:58 ` dominiq at lps dot ens.fr 2013-07-30 17:59 ` dominiq at lps dot ens.fr 2013-07-30 18:02 ` sgk at troutmask dot apl.washington.edu 2013-07-30 18:16 ` dominiq at lps dot ens.fr 2013-07-30 19:07 ` sgk at troutmask dot apl.washington.edu 2013-07-31 19:37 ` sgk at troutmask dot apl.washington.edu
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-58001-4-dtyP9g3Cby@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).