public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tobias dot burnus at physik dot fu-berlin dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/27304] gfortran: Warn/abort when format in write does not fit passed arguments
Date: Tue, 25 Apr 2006 17:24:00 -0000	[thread overview]
Message-ID: <20060425172407.8437.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27304-1719@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from tobias dot burnus at physik dot fu-berlin dot de  2006-04-25 17:24 -------
Post scriptum:
I actually see two bugs here:

(a) for static format strings, the test should be done at the compile time
(possibly also for  c = '(''n'')'; write(*,c) n )
-> see NAG compiler

(b) for dynamically created format strings, I think one should "crash" with a
meaningful error message. At least that is what ifort, g95, NAG and pgf95 do. I
like the error message of g95:
---------------
At line 5 of file test.f90 (Unit 6)
Fortran runtime error: Exhausted data descriptors in format
('n')
---------------
(other wording in NAG f95: "No data edit descriptor in tail of format
specification after reversion" [and no line number])


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27304


  reply	other threads:[~2006-04-25 17:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-25 11:30 [Bug fortran/27304] New: " tobias dot burnus at physik dot fu-berlin dot de
2006-04-25 17:24 ` tobias dot burnus at physik dot fu-berlin dot de [this message]
2006-04-25 18:33 ` [Bug fortran/27304] " pinskia at gcc dot gnu dot org
2006-04-26  4:10 ` jvdelisle at gcc dot gnu dot org
2006-04-26  6:22 ` tobias dot burnus at physik dot fu-berlin dot de
2006-04-26 22:53 ` jvdelisle at gcc dot gnu dot org
2006-04-27  5:50 ` patchapp at dberlin dot org
2006-04-27  6:02 ` jvdelisle at gcc dot gnu dot org
2006-04-27  8:09 ` burnus at net-b dot de
2006-04-28 23:55 ` jvdelisle at gcc dot gnu dot org
2006-04-29  0:02 ` jvdelisle at gcc dot gnu dot org
2006-04-30 20:59 ` jvdelisle at gcc dot gnu dot org
2006-04-30 21:02 ` jvdelisle at gcc dot gnu dot org
2006-04-30 21:03 ` jvdelisle at gcc dot gnu dot org
2006-05-02  8:37 ` tobias dot burnus at physik dot fu-berlin dot de
2006-05-04 19:10 ` tobias dot burnus at physik dot fu-berlin dot de
2006-05-05  0:13 ` jvdelisle at gcc dot gnu dot org
2006-05-05  7:04 ` fxcoudert at gcc dot gnu dot org
2006-05-09 20:16 ` tobias dot burnus at physik dot fu-berlin dot de
2006-05-09 22:10 ` fxcoudert 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=20060425172407.8437.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).