public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sgk at troutmask dot apl dot washington dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/32987] TAB in FORMAT: accept extension, warn with -std=f* Date: Sat, 04 Aug 2007 17:00:00 -0000 [thread overview] Message-ID: <20070804170032.20181.qmail@sourceware.org> (raw) In-Reply-To: <bug-32987-12095@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from sgk at troutmask dot apl dot washington dot edu 2007-08-04 17:00 ------- Subject: Re: TAB in FORMAT: accept extension, warn with -std=f* On Sat, Aug 04, 2007 at 04:53:33PM -0000, burnus at gcc dot gnu dot org wrote: > > > I therefore suggest: > - Silently accept the tab in libgfortran I disagree on this point. gfortran has been around for a long time now and this is the first report of the tab-in-format runtime error. gfortran should complain loudly that the code is invalid. > - Give a warning or an error with -std=f95/f2003. What about -std=f66, f77, or f90? Yes, I know gfortran doesn't have these levels, but the tab violates all fortran standards. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32987
next prev parent reply other threads:[~2007-08-04 17:00 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-08-04 13:55 [Bug fortran/32987] New: GFortran FORMAT statement error satyaakam at yahoo dot co dot in 2007-08-04 13:56 ` [Bug fortran/32987] " satyaakam at yahoo dot co dot in 2007-08-04 15:56 ` kargl at gcc dot gnu dot org 2007-08-04 16:26 ` kargl at gcc dot gnu dot org 2007-08-04 16:53 ` [Bug fortran/32987] TAB in FORMAT: accept extension, warn with -std=f* burnus at gcc dot gnu dot org 2007-08-04 17:00 ` sgk at troutmask dot apl dot washington dot edu [this message] 2007-08-04 17:38 ` burnus at gcc dot gnu dot org 2007-08-04 17:40 ` patchapp at dberlin dot org 2007-08-09 22:03 ` burnus at gcc dot gnu dot org 2007-08-09 22:08 ` burnus at gcc dot gnu dot org 2007-08-10 3:27 ` satyaakam at yahoo dot co dot in 2007-08-10 3:50 ` sgk at troutmask dot apl dot washington dot edu 2007-08-14 13:46 ` fxcoudert at gcc dot gnu dot org 2007-08-30 21:53 ` fago at caltech dot edu 2007-08-30 22:24 ` sgk at troutmask dot apl dot washington dot 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=20070804170032.20181.qmail@sourceware.org \ --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).