From: David Mosberger <davidm@napali.hpl.hp.com>
To: Jakub Jelinek <jakub@redhat.com>, libc-hacker@sources.redhat.com
Cc: davidm@hpl.hp.com
Subject: Re: ia64 libm update
Date: Wed, 24 Nov 2004 05:33:00 -0000 [thread overview]
Message-ID: <16804.7448.707805.82097@napali.hpl.hp.com> (raw)
In-Reply-To: <16798.20460.845793.758104@napali.hpl.hp.com>
The latest ia64 libm update patch is now available at:
ftp://ftp.hpl.hp.com/pub/linux-ia64/libc-intel-libm-v2.1-update-041123.diff.gz
md5sum: 51f780c07a7467281d038f49de33c8d9
The only difference compared to the previous version is that I removed
the temporary workaround for the tgamma() functions since HJ Lu's
patch to fix those routines has been checked in. Thus, "make check"
again succeeds without any failures.
Please apply.
Thanks,
--david
PS: For completeness, here is a diff between the previous and current
version of the patch.
--- ../libc-intel-libm-v2.1-update-041119.diff 2004-11-19 11:50:50.000000000 -0800
+++ ../libc-intel-libm-v2.1-update-041123.diff 2004-11-23 19:00:01.525722394 -0800
@@ -157944,7 +157944,7 @@
Index: sysdeps/ia64/fpu/w_tgamma.S
--- /dev/null
+++ sysdeps/ia64/fpu/w_tgamma.S
-@@ -0,0 +1,1839 @@
+@@ -0,0 +1,1835 @@
+.file "tgamma.s"
+
+
@@ -159710,11 +159710,7 @@
+.pred.rel "mutex",p7,p8
+{ .mfi
+(p7) mov GR_TAG = 259 // negative
-+#ifdef _LIBC
-+(p7) frcpa.s0 f8,p0 = f0,f0 // Get QNaN, and raise invalid
-+#else
+(p7) frcpa.s0 f8,p0 = f1,f8
-+#endif
+ nop.i 0
+}
+{ .mib
@@ -159787,7 +159783,7 @@
Index: sysdeps/ia64/fpu/w_tgammaf.S
--- /dev/null
+++ sysdeps/ia64/fpu/w_tgammaf.S
-@@ -0,0 +1,1332 @@
+@@ -0,0 +1,1328 @@
+.file "tgammaf.s"
+
+
@@ -161046,11 +161042,7 @@
+.pred.rel "mutex",p7,p8
+{ .mfi
+(p7) mov GR_TAG = 262 // negative
-+#ifdef _LIBC
-+(p7) frcpa.s0 f8,p0 = f0,f0 // Get QNaN, and raise invalid
-+#else
+(p7) frcpa.s0 f8,p0 = f1,f8
-+#endif
+ nop.i 0
+}
+{ .mib
@@ -161123,7 +161115,7 @@
Index: sysdeps/ia64/fpu/w_tgammal.S
--- /dev/null
+++ sysdeps/ia64/fpu/w_tgammal.S
-@@ -0,0 +1,4489 @@
+@@ -0,0 +1,4485 @@
+.file "tgammal.s"
+
+
@@ -165438,11 +165430,7 @@
+.pred.rel "mutex",p7,p8
+{ .mfi
+(p7) mov GR_Parameter_TAG = 256 // negative
-+#ifdef _LIBC
-+(p7) frcpa.s0 f8,p0 = f0,f0 // Get QNaN, and raise invalid
-+#else
+(p7) frcpa.s0 f8,p0 = f1,f8 // Raise V flag
-+#endif
+ nop.i 0
+}
+{ .mfb
next prev parent reply other threads:[~2004-11-24 5:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 7:47 David Mosberger
2004-11-19 8:43 ` Jakub Jelinek
2004-11-19 19:56 ` David Mosberger
2004-11-24 5:33 ` David Mosberger [this message]
2005-03-08 18:11 ` ia64 libm update broke nextafterl Jakub Jelinek
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=16804.7448.707805.82097@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=davidm@hpl.hp.com \
--cc=jakub@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).