public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/48298] F2003 Implement User Defined Derived Type IO (DTIO)
Date: Mon, 28 Mar 2011 08:49:00 -0000 [thread overview]
Message-ID: <bug-48298-4-U1K6gQmJIM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48298-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48298
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-03-28 07:48:51 UTC ---
(In reply to comment #1)
> Created attachment 23785 [details]
> A starting front end only patch
+ if (gfc_notify_std (GFC_STD_F2003, "Fortran 2003: DT format "
+ "specifier not allowed at %C") == FAILURE)
I somehow have parse problems; it sounds to me as if in Fortran 2003 the DT
specifier is not allowed. I would use:
+ if (gfc_notify_std (GFC_STD_F2003, "Fortran 2003: DT format "
+ "specifier at %C") == FAILURE)
next prev parent reply other threads:[~2011-03-28 7:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 15:51 [Bug fortran/48298] New: " jvdelisle at gcc dot gnu.org
2011-03-27 23:08 ` [Bug fortran/48298] " jvdelisle at gcc dot gnu.org
2011-03-28 5:41 ` jvdelisle at gcc dot gnu.org
2011-03-28 8:49 ` burnus at gcc dot gnu.org [this message]
2011-05-02 13:10 ` jvdelisle at gcc dot gnu.org
2011-09-07 22:21 ` [Bug fortran/48298] [F03] User-Defined Derived-Type " janus at gcc dot gnu.org
2013-06-16 14:39 ` dominiq at lps dot ens.fr
2013-10-23 8:09 ` damian at rouson dot net
2014-10-03 1:59 ` jvdelisle at gcc dot gnu.org
2014-10-03 4:45 ` damian at sourceryinstitute dot org
2014-10-03 5:15 ` kargl at gcc dot gnu.org
2014-10-03 5:21 ` damian at sourceryinstitute dot org
2014-10-03 13:27 ` jvdelisle at gcc dot gnu.org
2015-09-07 22:20 ` jvdelisle at gcc dot gnu.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-48298-4-U1K6gQmJIM@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).