public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jb at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/30605] New: -Wno-tabs should be active for -std=f2003 and -pedantic Date: Fri, 26 Jan 2007 22:18:00 -0000 [thread overview] Message-ID: <bug-30605-11659@http.gcc.gnu.org/bugzilla/> (raw) -Wno-tabs according to the manual currently is active for -pedantic, -std=f95, and -Wall. It should be active for -std=f2003 as well. Finally, it's not actually active for -pedantic. % cat xtabs.f90 print *, "hi" end -std=f2003 and -pedantic don't work: % gfortran -std=f2003 xtabs.f90 % % gfortran -pedantic xtabs.f90 % -std=f95 and -Wall do work: % gfortran -std=f95 xtabs.f90 xtabs.f90:1.1: print *, "hi" 1 Warning: Nonconforming tab character at (1) % gfortran -Wall xtabs.f90 xtabs.f90:1.1: print *, "hi" 1 Warning: Nonconforming tab character at (1) -- Summary: -Wno-tabs should be active for -std=f2003 and -pedantic Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jb at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30605
next reply other threads:[~2007-01-26 22:18 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-26 22:18 jb at gcc dot gnu dot org [this message] 2007-01-27 0:02 ` [Bug fortran/30605] " kargl at gcc dot gnu dot org 2007-01-27 0:02 ` kargl at gcc dot gnu dot org 2007-01-27 0:45 ` kargl at gcc dot gnu dot org 2007-01-27 18:01 ` kargl at gcc dot gnu dot org 2007-01-30 23:06 ` jb at gcc dot gnu dot org 2007-01-30 23:09 ` sgk at troutmask dot apl dot washington dot edu 2007-02-01 11:30 ` jb at gcc dot gnu dot org 2007-02-04 21:32 ` [Bug fortran/30605] [4.2 only] " kargl at gcc dot gnu dot org 2007-02-06 0:28 ` kargl at gcc dot gnu dot org 2007-02-06 0:31 ` kargl at gcc dot gnu dot 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-30605-11659@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).