From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: [PATCH] Clarify README.libm-test
Date: Wed, 24 Mar 2004 21:52:00 -0000 [thread overview]
Message-ID: <20040324132132.GL15946@sunsite.ms.mff.cuni.cz> (raw)
Hi!
The description in libm test README is quite confusing, because the tests
append to ULPs file instead of overwriting it each time, so there
is no need to move and concat the files together, on the other side
it is needed to remove pre-existing ULPs file before starting the tests.
2004-03-24 Jakub Jelinek <jakub@redhat.com>
* math/README.libm-test: Adjust description, since test-* append
to ULPs instead of overwriting it.
--- libc/math/README.libm-test.jj 1999-10-25 22:12:32.000000000 +0200
+++ libc/math/README.libm-test 2004-03-24 13:31:19.336961745 +0100
@@ -45,15 +45,15 @@ but it's better to pretty print it first
to generate a pretty-printed and sorted new ULPs file from the output
of the test drivers.
-To generate a new "libm-test-ulps" file, you can execute for example:
+To generate a new "libm-test-ulps" file, first remove "ULPs" file in the
+current directory, then you can execute for example:
test-double -u --ignore-max-ulp=yes
This generates a file "ULPs" with all double ULPs in it, ignoring any
previous calculated ULPs.
-Now move this away, e.g. "mv ULPs allULPs" and generate the ULPs
-for all other formats and concat all ULP files together (e.g. "cat
-ULPs >> allULPs"). As final step run "gen-libm-test.pl" with the file
-as input and ask to generate a pretty printed output in the file "NewUlps":
- gen-libm-test.pl -u allULPs -n
+Now generate the ULPs for all other formats, the tests will be appending
+the data to the "ULPs" file. As final step run "gen-libm-test.pl" with the
+file as input and ask to generate a pretty printed output in the file "NewUlps":
+ gen-libm-test.pl -u ULPs -n
Now you can rename "NewUlps" to "libm-test-ulps" and move it into
sysdeps.
Jakub
reply other threads:[~2004-03-24 15:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040324132132.GL15946@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.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).