From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: gfortran 9.3 write format error
Date: Sat, 18 Apr 2020 13:00:06 -0400 [thread overview]
Message-ID: <5f8e7366-dc52-ab99-c2fb-6cbbc19ee73f@cs.umass.edu> (raw)
In-Reply-To: <be58fb92-26f1-a7af-05fe-443fa8c61618@SystematicSw.ab.ca>
> As I did not recognize 1p[23]e... as a repeated format, it is possible that
> gfortran now requires you to specify that in a more standards compliant manner,
> except perhaps if you compile with -std=legacy (and the runtime supports that in
> formatted I/O format strings), otherwise you may want to try restating your
> formats in a more standard manner e.g.
>
> '(i6,3(1pe9.2),x,e9.2,x,0pf6.3,x,2(1pe10.2),''@'')'
>
> which may or may not solve your problem.
Or maybe write 1p,3e9.2 since the scale factor thing is actually a separate
format element (I believe, from cruising what general Fortran docs I found
around the Internet).
Best - Eliot
next prev parent reply other threads:[~2020-04-18 17:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d04d793a-6c8b-7a11-5a9b-5cda1bb86e50.ref@bellsouth.net>
2020-04-17 18:42 ` cygwin gfortran segfaulting on valid write statements worsafe
2020-04-17 19:39 ` Marco Atzeri
2020-04-17 22:29 ` Charles Russell
2020-04-17 19:42 ` Brian Inglis
2020-04-17 19:46 ` Brian Inglis
2020-04-17 23:33 ` Charles Russell
2020-04-18 1:01 ` Brian Inglis
[not found] ` <f868b6d5-2aee-c314-8a90-ba86a6aeeca6@bellsouth.net>
2020-04-18 16:23 ` gfortran 9.3 write format error (was: segfaulting on valid write statements) Brian Inglis
2020-04-18 17:00 ` Eliot Moss [this message]
2020-04-18 18:13 ` gfortran 9.3 write format error Charles Russell
2020-04-18 18:45 ` worsafe
2020-04-18 18:52 ` worsafe
2020-04-18 20:12 ` Charles Russell
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=5f8e7366-dc52-ab99-c2fb-6cbbc19ee73f@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.com \
/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).