From: Segher Boessenkool <segher@kernel.crashing.org>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
fortran <fortran@gcc.gnu.org>, David Edelsohn <dje.gcc@gmail.com>,
Harald Anlauf <anlauf@gmx.de>
Subject: Re: [Patch] Testsuite/Fortran: gfortran.dg/pr96711.f90 - fix expected value for PowerPC [PR96983]
Date: Wed, 19 May 2021 10:15:58 -0500 [thread overview]
Message-ID: <20210519151558.GK10366@gate.crashing.org> (raw)
In-Reply-To: <dbcdeff7-c954-5efc-efb4-aa5a312c38e6@codesourcery.com>
On Wed, May 19, 2021 at 02:32:02PM +0200, Tobias Burnus wrote:
> Regarding gfortran.dg/pr96711.f90:
>
> On my x86-64-gnu-linux, it PASSes.
> On our powerpc64le-linux-gnu it FAILS with
> 'STOP 3' (→ also scan-dump count) and 'STOP 4'.
>
> Contrary to PR96983's bug summary, I don't get an ICE.
>
>
> On powerpc64le-linux-gnu, the following condition evaluates true (→ 'STOP
> 3'):
>
> real(16) :: y ! 128bit REAL
> integer(16), parameter :: k2 = nint (2 / epsilon (y), kind(k2))
> integer(16), parameter :: m2 = 10384593717069655257060992658440192_16
> !2**113
> if (k2 /= m2) stop 3
>
> On x86_64-linux-gnu, k2 == m2 — but on powerpc64le-linux-gnu,
> k2 == 2**106 instead of 2**113.
>
> My solution is to permit also 2**106 besides 2**113.
>
> @PowerPC maintainers: Does this make sense? – It seems to work on our
> PowerPC
> but with all the new 'long double' changes, does it also work for you?
I do not understand Fortran well enough, could you explain what the code
is supposed to do?
> PR fortran/96983
> * gfortran.dg/pr96711.f90:
You're missing the actual entry here, fwiw.
> - integer(16), parameter :: m2 = 10384593717069655257060992658440192_16 !2**113
> + integer(16), parameter :: m2 = 10384593717069655257060992658440192_16 !2**113 ! Some systems like x86-64
> + integer(16), parameter :: m2a = 81129638414606681695789005144064_16 !2**106 ! Some systems like PowerPC
If you use double-double ("ibm long double") a number is represented as
the sum of two double precision numbers, while if you use IEEE quad
precision floating point you get a 112-bit fraction (and a leading one).
The most significant of the two DP numbers is the whole rounded to DP.
The actual precision varies, it depends on various factors :-/
Segher
> integer(16), volatile :: m
> x = 2 / epsilon (x)
> y = 2 / epsilon (y)
> m = nint (x, kind(m))
> ! print *, m
> if (k1 /= m1) stop 1
> if (m /= m1) stop 2
> m = nint (y, kind(m))
> ! print *, m
> - if (k2 /= m2) stop 3
> - if (m /= m2) stop 4
> + if (k2 /= m2 .and. k2 /= m2a) stop 3
> + if (m /= m2 .and. m /= m2a) stop 4
> end program
next prev parent reply other threads:[~2021-05-19 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 12:32 Tobias Burnus
2021-05-19 15:15 ` Segher Boessenkool [this message]
2021-05-19 18:35 ` Tobias Burnus
2021-05-19 20:39 ` Bernhard Reutner-Fischer
2021-05-19 21:30 ` Bernhard Reutner-Fischer
2021-05-19 21:41 ` Tobias Burnus
2021-05-19 23:54 ` Segher Boessenkool
2021-05-20 6:57 ` Aw: " Harald Anlauf
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=20210519151558.GK10366@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=anlauf@gmx.de \
--cc=dje.gcc@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tobias@codesourcery.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).