From: Richard Henderson <rth@twiddle.net>
To: libc-ports@sourceware.org
Subject: [PATCH 1/2] alpha: Fix compat version number for nearbyintl
Date: Tue, 14 Aug 2012 01:20:00 -0000 [thread overview]
Message-ID: <1344907219-22247-1-git-send-email-rth@twiddle.net> (raw)
---
ports/ChangeLog.alpha | 7 ++++++-
ports/sysdeps/alpha/fpu/s_nearbyint.c | 4 ++--
2 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/ports/ChangeLog.alpha b/ports/ChangeLog.alpha
index 97c4db6..e65097a 100644
--- a/ports/ChangeLog.alpha
+++ b/ports/ChangeLog.alpha
@@ -1,9 +1,14 @@
+2012-08-13 Richard Henderson <rth@twiddle.net>
+
+ * sysdeps/alpha/fpu/s_nearbyint.c (nearbyintl): Do compat
+ with GLIBC_2_1.
+
2012-08-08 Joseph Myers <joseph@codesourcery.com>
* sysdeps/unix/sysv/linux/alpha/kernel-features.h
(__ASSUME_TGKILL): Remove.
-2012-08-08 Richard Henderson <rth@redhat.com>
+2012-08-08 Richard Henderson <rth@twiddle.net>
* sysdeps/unix/sysv/linux/alpha/kernel-features.h
(__ASSUME_IEEE_RAISE_EXCEPTION): Remove.
diff --git a/ports/sysdeps/alpha/fpu/s_nearbyint.c b/ports/sysdeps/alpha/fpu/s_nearbyint.c
index 4589bfc..19ed06b 100644
--- a/ports/sysdeps/alpha/fpu/s_nearbyint.c
+++ b/ports/sysdeps/alpha/fpu/s_nearbyint.c
@@ -43,6 +43,6 @@ weak_alias (__nearbyint, nearbyint)
strong_alias (__nearbyint, __nearbyintl)
weak_alias (__nearbyint, nearbyintl)
#endif
-#if LONG_DOUBLE_COMPAT(libm, GLIBC_2_0)
-compat_symbol (libm, __nearbyint, nearbyintl, GLIBC_2_0);
+#if LONG_DOUBLE_COMPAT(libm, GLIBC_2_1)
+compat_symbol (libm, __nearbyint, nearbyintl, GLIBC_2_1);
#endif
--
1.7.7.6
next reply other threads:[~2012-08-14 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 1:20 Richard Henderson [this message]
2012-08-14 1:20 ` [PATCH 2/2] alpha: Don't test toolchain support for TLS or GPREL Richard Henderson
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=1344907219-22247-1-git-send-email-rth@twiddle.net \
--to=rth@twiddle.net \
--cc=libc-ports@sourceware.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).