From: "Atwood, Robert C" <r.atwood@imperial.ac.uk>
To: <gcc-help@gcc.gnu.org>
Subject: RE: gFortran problem compiling complex character strings
Date: Mon, 17 Dec 2007 14:09:00 -0000 [thread overview]
Message-ID: <2CB39EAF0E0EFF498ADEDA636B8C999F05574A8E@icex1.ic.ac.uk> (raw)
In-Reply-To: <4764027A.9020300@tuckley.org>
dominique> > Colin, your line is too long for the fixed form implied by
dominique> the .f suffix:
colin> Argh! Yes, of course. It must be that g77 didn't have that
colin> limit since the
colin> program used to build ok with that.
Now I am curious why that would be, I was under the impression that (in
absence of any flags) the 72 char was the default in g77?
Did you have a Makefile or other build system that had some additional
flags when using g77?
(I am in the positon of helping Fortran users get their programs working
without actually being a Fortran user so little bits of info like this
are useful!)
man g77 says:
-ffixed-line-length-n
Set column after which characters are ignored in typical
fixed-form lines in the source file, and through which spaces are
assumed (as if padded to that length) after the ends of short
fixed-form lines.
Popular values for n include 72 (the standard and the
default), 80 (card image), and 132 ...
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
next prev parent reply other threads:[~2007-12-17 14:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 16:10 Dominique Dhumieres
2007-12-15 16:17 ` John (Eljay) Love-Jensen
2007-12-15 16:36 ` Colin Tuckley
2007-12-17 14:09 ` Atwood, Robert C [this message]
2007-12-17 14:15 ` John Love-Jensen
2007-12-17 14:34 ` Atwood, Robert C
2007-12-17 15:05 ` Colin Tuckley
2007-12-17 15:29 ` Atwood, Robert C
-- strict thread matches above, loose matches on Subject: below --
2007-12-14 8:53 Colin Tuckley
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=2CB39EAF0E0EFF498ADEDA636B8C999F05574A8E@icex1.ic.ac.uk \
--to=r.atwood@imperial.ac.uk \
--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).