From: Jorge D'Elia <jdelia@santafe-conicet.gov.ar>
To: Gfortran List <fortran@gcc.gnu.org>
Subject: coarrays using extended precision (80 bits) ?
Date: Fri, 21 Apr 2023 08:33:31 -0300 (ART) [thread overview]
Message-ID: <328135304.91027.1682076811330.JavaMail.zimbra@santafe-conicet.gov.ar> (raw)
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
Dear GFortran developers,
One question: is there any chance of encoding with coarrays using
extended precision (80 bits) at least inside a multicore computer?
(as if to simplify a bit).
To date, the possibility of using double precision (64 bits) or
extended precision (80 bits) is an alternative in our production
code, but sometimes we would like to do computations in
80 bits and, in certain parts, there are coarrays.
We have validated even in quadruple precision (128 bits), using
ifort although, as is well known, the CPU times are largely
excessive.
Thanks in any case.
Regards.
Jorge.
CIMEC (UNL-CONICET), [ http://www.cimec.org.ar/ | www.cimec.org.ar ]
--
next reply other threads:[~2023-04-21 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 11:33 Jorge D'Elia [this message]
2023-04-21 22:53 ` Steve Kargl
2023-04-22 10:46 ` Jorge D'Elia
2023-04-22 13:07 ` Steve Kargl
2023-04-22 23:26 ` Jorge D'Elia
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=328135304.91027.1682076811330.JavaMail.zimbra@santafe-conicet.gov.ar \
--to=jdelia@santafe-conicet.gov.ar \
--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).