From: Joseph Myers <joseph@codesourcery.com>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Cc: Szabolcs Nagy <Szabolcs.Nagy@arm.com>, nd <nd@arm.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] update libm-test-ulps for new exp
Date: Thu, 19 Jul 2018 17:23:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1807191717050.27771@digraph.polyomino.org.uk> (raw)
In-Reply-To: <DB5PR08MB103099E0562C1C80083E531983520@DB5PR08MB1030.eurprd08.prod.outlook.com>
On Thu, 19 Jul 2018, Wilco Dijkstra wrote:
> Would it be feasible to include a generic ulp file which sets the
> expected ulps into the target ulp files that add or override such
> settings? That way most ulp files could be significantly reduced and
> only targets with special formats may need to have more entries. Also
> this would make it clearer when there are anomalies and possible ulp
> errors that need to be fixed.
One could construct various such schemes, yes, at least for float and
double ulps (but being able to share ldbl-128 ulps would be a good idea as
well, including the same ulps being used for long double on some platforms
and _Float128 on others, it's not as if there are architecture-specific
ldbl-128 functions beyond fully-determined ones such as sqrtl and fmal -
though there are architecture variations in whether multiply and add might
get fused for float128).
I'd suggest a requirement for any such scheme should be code sharing
between ulps file parsing for libm tests (gen-libm-test.pl) and the manual
(libm-err-tab.pl). We probably want to finish getting consensus on the
use of Python to replace Perl (and possibly awk) in the build first.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-07-19 17:23 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 8:49 [PATCH 00/10] Optimized math routines Szabolcs Nagy
2018-07-06 8:57 ` [PATCH 01/10] Clean up converttoint handling and document the semantics Szabolcs Nagy
2018-08-07 19:52 ` Joseph Myers
2018-07-06 8:57 ` [PATCH 02/10] Improve performance of sincosf Szabolcs Nagy
2018-07-11 13:22 ` Szabolcs Nagy
2018-08-07 20:11 ` Joseph Myers
2018-08-10 12:12 ` Wilco Dijkstra
2018-08-10 16:04 ` Joseph Myers
2018-07-06 8:59 ` [PATCH 03/10] Improve performance of sinf and cosf Szabolcs Nagy
2018-08-13 19:46 ` Joseph Myers
2018-08-14 19:41 ` Joseph Myers
2018-08-15 13:11 ` Wilco Dijkstra
2018-07-06 9:02 ` [PATCH 04/10] Add new exp and exp2 implementations Szabolcs Nagy
2018-08-22 19:55 ` Joseph Myers
2018-09-05 15:26 ` Szabolcs Nagy
2018-07-06 9:04 ` [PATCH 05/10] aarch64: update libm-test-ulps Szabolcs Nagy
2018-08-24 17:09 ` Joseph Myers
2018-07-06 9:05 ` [PATCH 06/10] arm: " Szabolcs Nagy
2018-07-06 9:06 ` [PATCH 07/10] x86_64: " Szabolcs Nagy
2018-07-06 9:08 ` [PATCH 08/10] Add new log implementation Szabolcs Nagy
2018-08-24 17:19 ` Joseph Myers
2018-07-06 9:09 ` [PATCH 09/10] Add new log2 implementation Szabolcs Nagy
2018-07-06 9:10 ` [PATCH 10/10] Add new pow implementation Szabolcs Nagy
2018-07-11 13:24 ` Szabolcs Nagy
2018-07-06 12:43 ` [PATCH 00/10] Optimized math routines Carlos O'Donell
2018-07-06 15:46 ` Szabolcs Nagy
2018-07-06 16:27 ` Carlos O'Donell
2018-07-06 17:17 ` Szabolcs Nagy
2018-07-09 12:15 ` Szabolcs Nagy
2018-07-09 13:09 ` Adhemerval Zanella
2018-07-09 13:35 ` Szabolcs Nagy
2018-07-09 14:27 ` Adhemerval Zanella
2018-07-09 15:41 ` Szabolcs Nagy
2018-07-09 18:20 ` Adhemerval Zanella
2018-07-17 21:59 ` Joseph Myers
2018-07-18 0:07 ` Carlos O'Donell
2018-07-11 13:39 ` Szabolcs Nagy
2018-07-11 14:19 ` [PATCH] powerpc: update libm-test-ulps Szabolcs Nagy
2018-07-12 15:52 ` [PATCH] update libm-test-ulps for new exp Szabolcs Nagy
2018-07-18 17:25 ` Joseph Myers
2018-07-19 9:15 ` Szabolcs Nagy
2018-07-19 17:03 ` Joseph Myers
2018-07-19 17:15 ` Wilco Dijkstra
2018-07-19 17:23 ` Joseph Myers [this message]
2018-08-07 11:03 ` [PATCH 00/10] Optimized math routines Szabolcs Nagy
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=alpine.DEB.2.20.1807191717050.27771@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Szabolcs.Nagy@arm.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.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).