public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/93727] Fortran 2018: EX edit descriptor
Date: Sun, 10 Mar 2024 03:37:13 +0000	[thread overview]
Message-ID: <bug-93727-4-NsCSWuXQIU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93727-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93727

--- Comment #5 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
I have been studying this a bit by looking at the 2023 std and functionality of
printf().
Specifically printf() provides the 'A' descriptor which can be used for float
(kind=4) and double (kind=8).  It will accept a long double (80 bit aka
kind=10). I am noticing that the results of double and long double are
identical, no extra precision visible. It is very possible I am not doing that
correctly.

I do not see anything related to quad precision floats.  I am posting this as i
think we will have to do some of our own translating byte portions of floats
ourselves. Portability may be an issue. For example IBM 360 128bit precision or
some other processor may not follow the same internal representations.

Regardless I have preliminary code for the frontend that results in calling
anew fucntion write_ex in transfer.c

I think that kind=4 and kind=8 will be fine. Any thoughts on kind=10 or kind=16
I would appreciate as I further explore this.

  parent reply	other threads:[~2024-03-10  3:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-93727-4@http.gcc.gnu.org/bugzilla/>
2020-07-12 15:38 ` dominiq at lps dot ens.fr
2020-07-14 12:51 ` jvdelisle at charter dot net
2020-08-11 14:41 ` dominiq at lps dot ens.fr
2020-08-14 21:34 ` jvdelisle at charter dot net
2020-08-29 18:04 ` jvdelisle at charter dot net
2024-03-06  2:34 ` jvdelisle at gcc dot gnu.org
2024-03-10  3:37 ` jvdelisle at gcc dot gnu.org [this message]
2024-03-10  9:41 ` thenlich at gcc dot gnu.org
2024-03-10 17:17 ` jvdelisle at gcc dot gnu.org

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=bug-93727-4-NsCSWuXQIU@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).