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: Thu, 30 Aug 2007 22:24:00 -0000 [thread overview]
Message-ID: <20070830222431.25917.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32987-12095@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from sgk at troutmask dot apl dot washington dot edu 2007-08-30 22:24 -------
Subject: Re: TAB in FORMAT: accept extension, warn with -std=f*
On Thu, Aug 30, 2007 at 09:52:56PM -0000, fago at caltech dot edu wrote:
>
> ------- Comment #12 from fago at caltech dot edu 2007-08-30 21:52 -------
> A stupid question: why cannot gfortran detect this invalid code at compile
> time? I was quite surprised by a runtime error.
>
See comment #9 in bugzilla.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32987
prev parent reply other threads:[~2007-08-30 22:24 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
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 [this message]
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=20070830222431.25917.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: 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).