From: Charles Russell <worsafe@bellsouth.net>
To: cygwin cygwin <cygwin@cygwin.com>
Subject: Re: gfortran 9.3 write format error
Date: Sat, 18 Apr 2020 13:13:30 -0500 [thread overview]
Message-ID: <2593fa5a-84dd-dadd-ea84-d16d465965db@bellsouth.net> (raw)
In-Reply-To: <be58fb92-26f1-a7af-05fe-443fa8c61618@SystematicSw.ab.ca>
On 4/18/2020 11:23 AM, Brian Inglis wrote:
what compiler version are you using on Debian
$ gfortran --version
GNU Fortran (Debian 8.3.0-6) 8.3.0
When support ended for g77 I feared for my collection of old fortran
code, but it all worked fine under gfortran after a few trivial changes
that I made years ago. (BLOCK DATA had to be rewritten, but I had used
that only once.) The gfortran developers must intend to keep viable all
that netlib code that has been widely used and thoroughly debugged. No
problems with the above gfortran version, which is newer than the most
recent one for Cygwin. So I doubt that the error message comes from
intentional compiler changes.
Like you, I can't understand why a syntax error should appear at run
time. gfortran is good at finding syntax errors at compile time.
I'm still using fortran 77 because it meets my needs, I know where the
bugs hide, and that is the language of most netlib code and of all my
old tools. gfortran handles it well.
next prev parent reply other threads:[~2020-04-18 18:18 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 ` gfortran 9.3 write format error Eliot Moss
2020-04-18 18:13 ` Charles Russell [this message]
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=2593fa5a-84dd-dadd-ea84-d16d465965db@bellsouth.net \
--to=worsafe@bellsouth.net \
--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).