From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@ge.com>
To: <gcc-help@gcc.gnu.org>
Subject: Gfortran issue
Date: Thu, 18 Sep 2008 14:21:00 -0000 [thread overview]
Message-ID: <8E460D1B58F94945A20AA70D4D41430D08DCC330@ALPMLVEM08.e2k.ad.ge.com> (raw)
Hi All
I am compiling legacy fortran 77 code which used VAX-Fortran type
parameterized formats, in gfortran version as below :
Target: powerpc-ibm-aix5.3.0.0
Configured with: /cots/gnu/gcc-4.2.3/configure --prefix=/opt/freeware
--with-gmp=/usr/local --with-mpfr=/usr/local
--enable-languages=c,c++,fortran
Thread model: aix
gcc version 4.2.3
I have a fortran program having the following lines of code among
others. These lines of code is what generats a compile error :
CHARACTER*(24*RT_MB_MAXMB) PNTNAME
........
WRITE(LO,220)
220 FORMAT(A<24*RT_MB_MAXMB>)
The error I get is : Error: Unexpected element in format string at (1).
Is there any way to get around this in gfortran. Works fine in g77 but
does not in gfortran. Your help and advice and pointers will be greatly
appreciated.
With Regards
Vardhan
next reply other threads:[~2008-09-18 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 14:21 Vardhan, Sundara (GE Infra, Energy) [this message]
2014-07-29 7:31 Jerome Huck
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=8E460D1B58F94945A20AA70D4D41430D08DCC330@ALPMLVEM08.e2k.ad.ge.com \
--to=sundara.vardhan@ge.com \
--cc=gcc-help@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).