From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>, Roland McGrath <roland@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: [PATCH] bits/mathinline.h
Date: Wed, 04 Jun 2003 20:20:00 -0000 [thread overview]
Message-ID: <20030604202053.GB24872@sunsite.ms.mff.cuni.cz> (raw)
Hi!
Bernds patch also put __sqrtl inside of __FAST_MATH__, but
__sqrtl is used by asinh, acosh, atanh and hypot outside of __FAST_MATH__.
2003-06-04 Jakub Jelinek <jakub@redhat.com>
* sysdeps/i386/fpu/bits/mathinline.h (log1p, asinh, acosh, atanh,
hypot, logb): Protect with #ifdef __FAST_MATH__.
2003-06-04 Thorsten Kukuk <kukuk@suse.de>
* sysdeps/i386/fpu/bits/mathinline.h (ldexpf, ldexpl): Protect with
#ifdef __FAST_MATH__.
--- libc/sysdeps/i386/fpu/bits/mathinline.h 2 Jun 2003 22:39:19 -0000 1.51
+++ libc/sysdeps/i386/fpu/bits/mathinline.h 4 Jun 2003 20:06:22 -0000
@@ -534,11 +534,10 @@ ldexp (double __x, int __y) __THROW
# ifdef __FAST_MATH__
__inline_mathcodeNP (expm1, __x, __expm1_code)
-# endif
/* We cannot rely on M_SQRT being defined. So we do it for ourself
here. */
-# define __M_SQRT2 1.41421356237309504880L /* sqrt(2) */
+# define __M_SQRT2 1.41421356237309504880L /* sqrt(2) */
__inline_mathcodeNP (log1p, __x, \
register long double __value; \
@@ -577,12 +576,12 @@ __inline_mathcodeNP(logb, __x, \
: "=t" (__junk), "=u" (__value) : "0" (__x)); \
return __value)
+# endif
#endif
#ifdef __USE_ISOC99
#ifdef __FAST_MATH__
__inline_mathop_declNP (log2, "fld1; fxch; fyl2x", "0" (__x) : "st(1)")
-#endif /* __FAST_MATH__ */
__MATH_INLINE float
ldexpf (float __x, int __y) __THROW
@@ -596,7 +595,6 @@ ldexpl (long double __x, int __y) __THRO
__ldexp_code;
}
-#ifdef __FAST_MATH__
__inline_mathcodeNP3 (fma, __x, __y, __z, return (__x * __y) + __z)
__inline_mathopNP (rint, "frndint")
Jakub
next reply other threads:[~2003-06-04 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 20:20 Jakub Jelinek [this message]
2003-06-04 21:33 ` Ulrich Drepper
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=20030604202053.GB24872@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@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).