public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Thomas Koenig <tkoenig@netcologne.de>,
	Michael Meissner <meissner@linux.ibm.com>,
	Segher Boessenkool <segher@kernel.crashing.org>,
	"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	Peter Bergner <bergner@linux.ibm.com>,
	Bill Schmidt <wschmidt@linux.ibm.com>,
	gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [power-ieee128] OPEN CONV
Date: Sat, 8 Jan 2022 12:10:56 +0100	[thread overview]
Message-ID: <20220108111056.GT2646553@tucnak> (raw)
In-Reply-To: <20220108110038.GS2646553@tucnak>

On Sat, Jan 08, 2022 at 12:00:38PM +0100, Jakub Jelinek via Gcc-patches wrote:
> And IMHO the default like for byte-swapping should be the native
> format, i.e. the one the program actually used.

One reason for that is that neither conversion is lossless, neither format
is a subset or superset of the other.  Yes, IEEE quad has both much bigger
exponent range (-16382..16383 vs. -1022..1023) and slightly bigger fixed
precision (113 vs. 106 bits).
But IBM extended has that weirdo numerically awful flexible precision where
certain numbers can have much bigger precision than those 106 bits, up to
2048+52 or so.  So there is rounding in both directions.
So, after distros switch to -mabi=ieeelongdouble by default or when people
use -mabi=ieeelongdouble on their programs, they'd better store that format
into data files by default, without the need of some magic CONVERT= options,
env vars or command line options.  Only in the case where they need to
interact with -mabi=ibmlongdouble environments, they need to take some
action.

	Jakub


  reply	other threads:[~2022-01-08 11:11 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 15:36 [power-ieee128] libgfortran: -mabi=ieeelongdouble I/O Jakub Jelinek
2022-01-03 16:26 ` Jakub Jelinek
2022-01-03 17:03   ` Thomas Koenig
2022-01-03 20:00     ` [power-ieee128] libgfortran, fortran: " Jakub Jelinek
2022-01-03 22:43       ` Thomas Koenig
2022-01-04 11:07         ` [power-ieee128] RFH: LTO broken Jakub Jelinek
2022-01-04 13:41           ` [power-ieee128] libgfortran: -mabi=ieeelongdouble I/O fix Jakub Jelinek
2022-01-04 14:35             ` Thomas Koenig
2022-01-06  2:48           ` [power-ieee128] RFH: LTO broken Michael Meissner
2022-01-06  4:17           ` Michael Meissner
2022-01-06  5:00           ` Michael Meissner
2022-01-06 20:01             ` Thomas Koenig
2022-01-06 20:10               ` Jakub Jelinek
2022-01-07  9:22               ` [power-ieee128] OPEN CONV Jakub Jelinek
2022-01-07 10:26                 ` Thomas Koenig
2022-01-07 19:52                   ` Jakub Jelinek
2022-01-07 21:40                     ` Thomas Koenig
2022-01-07 21:48                       ` Jakub Jelinek
2022-01-08 10:07                         ` Thomas Koenig
2022-01-08 11:00                           ` Jakub Jelinek
2022-01-08 11:10                             ` Jakub Jelinek [this message]
2022-01-08 14:02                               ` Jakub Jelinek
2022-01-08 14:13                                 ` Thomas Koenig
2022-01-08 14:18                                   ` Jakub Jelinek
2022-01-08 18:59                                     ` Michael Meissner
2022-01-08 19:15                                       ` David Edelsohn
2022-01-08 19:37                                         ` Michael Meissner
2022-01-07 11:29               ` [power-ieee128] RFH: LTO broken Jakub Jelinek
2022-01-07 13:31                 ` Jakub Jelinek
2022-01-07 14:25                   ` Thomas Koenig
2022-01-07 16:46                     ` Jakub Jelinek
2022-01-07 21:33                       ` Thomas Koenig
2022-01-03 16:48 ` [power-ieee128] libgfortran: -mabi=ieeelongdouble I/O Thomas Koenig

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=20220108111056.GT2646553@tucnak \
    --to=jakub@redhat.com \
    --cc=bergner@linux.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=meissner@linux.ibm.com \
    --cc=segher@kernel.crashing.org \
    --cc=tkoenig@netcologne.de \
    --cc=wschmidt@linux.ibm.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).