This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Support excess precision for integer / floating-point comparisons (PR c/87390)
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Christophe Lyon <christophe dot lyon at linaro dot org>
- Cc: gcc Patches <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 27 Sep 2018 19:29:12 +0000
- Subject: Re: Support excess precision for integer / floating-point comparisons (PR c/87390)
- References: <alpine.DEB.2.21.1809262114210.17757@digraph.polyomino.org.uk> <CAKdteOY5isz+RuK=epjDx6faCQ-mC0_ngkvmWYD8VciXGWFVFQ@mail.gmail.com>
On Thu, 27 Sep 2018, Christophe Lyon wrote:
> After this patch I've noticed regressions on
> fp-int-convert-float16-timode.c
> gcc.dg/torture/fp-int-convert-float16.c
> on aarch64 and arm (at execution time)
Does this patch help?
Index: gcc/testsuite/gcc.dg/torture/fp-int-convert.h
===================================================================
--- gcc/testsuite/gcc.dg/torture/fp-int-convert.h (revision 264666)
+++ gcc/testsuite/gcc.dg/torture/fp-int-convert.h (working copy)
@@ -90,6 +90,7 @@
if (ivin != (VAL) \
|| ((PREC_OK) && ivout != ivin) \
|| ((PREC_OK) && ivout != (VAL)) \
- || fv1 != (VAL) || fv2 != (VAL) || fv1 != fv2) \
+ || fv1 != (FT) (VAL) || fv2 != (FT) (VAL) \
+ || fv1 != fv2) \
abort (); \
} while (0)
--
Joseph S. Myers
joseph@codesourcery.com