public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Arjen Markus <arjen.markus895@gmail.com>
To: William Carter <carterwj64@yahoo.com>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: Interested in participating in Fortran study to compile very large modules
Date: Sun, 24 Apr 2022 16:38:56 +0200	[thread overview]
Message-ID: <CAMCbSMr+4Yt7r_yfM6JLncDpOgNps5RHAwo7hqKNZY6n+2_cXg@mail.gmail.com> (raw)
In-Reply-To: <1432045427.1382721.1650660377407@yahoo.com>

MicroSoft's Fortran compiler is a very old compiler that has not been
maintained in a very long time. The gfortran compiler and the Intel Fortran
oneAPI compiler, both freely available, would easily handle such arrays as
you mention. What system are you running on?

Regards,

Arjen

Op vr 22 apr. 2022 om 22:46 schreef William Carter via Fortran <
fortran@gcc.gnu.org>:

> Hello,
>
> I am an engineer for the nuclear power industry.  As part of my master’s
> thesis I developed a model of a fuel pin using Fortran.  At the time I was
> working with a cheap Microsoft compiler.  It was version 5.1 if I remember
> correctly.  My model does 3D finite differencing and is rather demanding on
> the compiler.  My Microsoft compiler was pretty limiting on the size of the
> modules I could compile.  Typically I was working with a 7x7x7 spatial
> array with a 5 properties at each node.  Everything was in double
> precision.  So it was 7x7x7x5.  I could juggle these around, but I had to
> say within this maximum or the compiler would not work.  I would like to
> work with MUCH larger arrays.  I am thinking 100x100x100x5.  Again in
> double precision. So I need a better compiler.  Can you help?
>
> Regards,
>
> Bill Carter
>
>
> Sent from Mail for Windows
>
>

  reply	other threads:[~2022-04-24 14:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22 20:46 William Carter
2022-04-24 14:38 ` Arjen Markus [this message]
2022-04-25 10:41   ` William Carter
2022-04-25 13:13     ` Arjen Markus
2022-04-25 14:50       ` William Carter

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=CAMCbSMr+4Yt7r_yfM6JLncDpOgNps5RHAwo7hqKNZY6n+2_cXg@mail.gmail.com \
    --to=arjen.markus895@gmail.com \
    --cc=carterwj64@yahoo.com \
    --cc=fortran@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).