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/28039] New: Warn when ignoring extra characters in the format specification
Date: Thu, 15 Jun 2006 11:10:00 -0000 [thread overview]
Message-ID: <bug-28039-1719@http.gcc.gnu.org/bugzilla/> (raw)
Assume the following case:
One had somewhere '(3(a,....),f)', now one copies this and realizes that one
does not need the 3(..) anymore. Result:
'(a,....),f)'
Ups, the ",f)" is ignored.
Currently, gfortran does not warn in such a case.
Expected: gfortran warns at compile time
Ifort (9.1) even default warns in such a case:
fortcom: Warning: test.f90, line 5: The extra characters in the format
specification will be ignored ['(a),f)']
write(*,'(a),f)') 'Hello', r
--------------^
Test case:
--------------
program test
implicit none
real :: r
r = 1.0
write(*,'(a),f)') 'Hello', r
end program test
--------------
--
Summary: Warn when ignoring extra characters in the format
specification
Product: gcc
Version: 4.2.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: tobias dot burnus at physik dot fu-berlin dot de
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28039
next reply other threads:[~2006-06-15 10:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 11:10 tobias dot burnus at physik dot fu-berlin dot de [this message]
2006-06-20 11:04 ` [Bug fortran/28039] " fxcoudert at gcc dot gnu dot org
2009-08-22 23:21 ` bdavis at gcc dot gnu dot org
2009-08-23 2:20 ` bdavis at gcc dot gnu dot org
2009-08-23 2:27 ` bdavis at gcc dot gnu dot org
2009-08-24 8:53 ` burnus at gcc dot gnu dot org
2009-08-26 23:10 ` hp at gcc dot gnu dot org
2009-08-27 6:29 ` burnus at gcc dot gnu dot org
2009-08-27 12:00 ` burnus at gcc dot gnu dot org
2009-08-27 12:11 ` burnus at gcc dot gnu dot org
2009-12-30 4:26 ` bdavis at gcc dot gnu dot org
2009-12-30 5:23 ` bdavis at gcc dot gnu dot org
2010-04-09 2:03 ` jvdelisle at gcc dot gnu dot org
2010-04-09 3:25 ` jvdelisle at gcc dot gnu dot org
2010-04-24 3:05 ` jvdelisle at gcc dot gnu dot org
2010-04-24 3:05 ` jvdelisle 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-28039-1719@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).