public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/107062] [13 regression] gfortran.dg/ieee/fma_1.f90 fails after r13-2577-g7c4c65d11469d2
Date: Wed, 28 Sep 2022 15:33:02 +0000 [thread overview]
Message-ID: <bug-107062-4-WNP3CG7cnD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107062-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107062
--- Comment #3 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
Hum, that one test for FMA is really unreliable. I think I need to remove it
altogether, it fails on x86 as well for float and double, if it also fails on
powerpc for long double, then let's get rid of it.
Can you confirm that the test pass if you apply the patch below? That will make
sure there is no failure further down the test.
diff --git a/gcc/testsuite/gfortran.dg/ieee/fma_1.f90
b/gcc/testsuite/gfortran.dg/ieee/fma_1.f90
index 34636426c98..320c73a0c3c 100644
--- a/gcc/testsuite/gfortran.dg/ieee/fma_1.f90
+++ b/gcc/testsuite/gfortran.dg/ieee/fma_1.f90
@@ -38,7 +38,6 @@
print *, sx1 * sx2 + sx3
print *, ieee_fma(sx1, sx2, sx3)
if (ieee_fma(sx1, sx2, sx3) /= real(3, kind(sx1)) / 2) stop 4
- !if (ieee_fma(sx1, sx2, sx3) == sx1 * sx2 + sx3) stop 5
! Double
@@ -57,7 +56,6 @@
print *, dx1 * dx2 + dx3
print *, ieee_fma(dx1, dx2, dx3)
if (ieee_fma(dx1, dx2, dx3) /= real(3, kind(dx1)) / 2) stop 4
- !if (ieee_fma(dx1, dx2, dx3) == dx1 * dx2 + dx3) stop 5
! Large kind 1
@@ -76,7 +74,6 @@
print *, lx1 * lx2 + lx3
print *, ieee_fma(lx1, lx2, lx3)
if (ieee_fma(lx1, lx2, lx3) /= real(3, kind(lx1)) / 2) stop 4
- if (ieee_fma(lx1, lx2, lx3) == lx1 * lx2 + lx3) stop 5
! Large kind 2
@@ -95,6 +92,5 @@
print *, wx1 * wx2 + wx3
print *, ieee_fma(wx1, wx2, wx3)
if (ieee_fma(wx1, wx2, wx3) /= real(3, kind(wx1)) / 2) stop 4
- if (ieee_fma(wx1, wx2, wx3) == wx1 * wx2 + wx3) stop 5
end
next prev parent reply other threads:[~2022-09-28 15:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 21:04 [Bug fortran/107062] New: " seurer at gcc dot gnu.org
2022-09-28 7:23 ` [Bug fortran/107062] " fxcoudert at gcc dot gnu.org
2022-09-28 14:57 ` seurer at gcc dot gnu.org
2022-09-28 15:24 ` fxcoudert at gcc dot gnu.org
2022-09-28 15:33 ` fxcoudert at gcc dot gnu.org [this message]
2022-09-28 16:52 ` seurer at gcc dot gnu.org
2022-09-29 8:11 ` rguenth at gcc dot gnu.org
2022-10-03 7:30 ` fxcoudert at gcc dot gnu.org
2022-10-03 7:30 ` fxcoudert 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-107062-4-WNP3CG7cnD@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).