public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <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 19:07:00 -0000	[thread overview]
Message-ID: <bug-58001-4-gMwrNQubxF@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

--- Comment #8 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Tue, Jul 30, 2013 at 06:16:27PM +0000, dominiq at lps dot ens.fr wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58001
> 
> --- Comment #7 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> > With -Wno-tabs, gfortran should report a warning for the
> > occurence of every tab used in the context of a character
> > from the Fortran character set.  Taking your code, which I've
> > deleted here, and replace all whitespace by tabs, I get the
> > expected number of warnings.  Historically, I wanted to use
> > -Wtabs as you expected, but there was too much wailing on 
> > the gfortran lists, so it was changed to -Wno-tabs with the
> > meaning that "no tabs are allowed" in the context of the
> > Fortran character set.  You'll notice that tabs within
> > a literal character string are not flagged.
> 
> I cannot understand the rationale of this choice, but I guess it's too late to
> change it!-(
> 
> > The history of -Wtabs verse -Wno-tabs can be found in the mailinglist
> > archive.
> 
> No interest to dig the archives on this issue.

http://gcc.gnu.org/ml/fortran/2006-03/msg00226.html


  parent reply	other threads:[~2013-07-30 19:07 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
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 [this message]
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-gMwrNQubxF@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: link
Be 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).