This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/6824] New: Usage of __LONGDOUBLE128 instead of __LONG_DOUBLE_128__ causes PowerPC checklocal-plt make check failure
- From: "rsa at us dot ibm dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 7 Aug 2008 21:58:40 -0000
- Subject: [Bug libc/6824] New: Usage of __LONGDOUBLE128 instead of __LONG_DOUBLE_128__ causes PowerPC checklocal-plt make check failure
- Reply-to: sourceware-bugzilla at sourceware dot org
Erroneous usage of __LONGDOUBLE128 (which was introduced to GCC for AIX support)
was causing mathinline.h to lack an implementation of __signbitl for powerpc32.
This caused checklocal-plt make check failure for PowerPC.
The correct define to use is __LONG_DOUBLE_128__.
diff -X /home/ryanarn/bin/dontdiff -uNr
glibc/sysdeps/unix/sysv/linux/powerpc/bits/mathinline.h
glibc.new/sysdeps/unix/sysv/linux/powerpc/bits/mathinline.h
--- glibc/sysdeps/unix/sysv/linux/powerpc/bits/mathinline.h 2008-08-07
10:54:03.000000000 -0500
+++ glibc.new/sysdeps/unix/sysv/linux/powerpc/bits/mathinline.h 2008-08-07
16:17:36.000000000 -0500
@@ -72,7 +72,7 @@
__extension__ union { double __d; int __i[2]; } __u = { __d: __x };
return __u.__i[0] < 0;
}
-# ifdef __LONGDOUBLE128
+# ifdef __LONG_DOUBLE_128__
__MATH_INLINE int
__NTH (__signbitl (long double __x))
{
I'll post this to mainline with a ChangeLog after full testing with GCC 4.1 &
GCC 4.3 compilers and on different PowerPC arches.
--
Summary: Usage of __LONGDOUBLE128 instead of __LONG_DOUBLE_128__
causes PowerPC checklocal-plt make check failure
Product: glibc
Version: 2.8
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper at redhat dot com
ReportedBy: rsa at us dot ibm dot com
CC: glibc-bugs at sources dot redhat dot com
GCC build triplet: powerpc64-linux
GCC host triplet: powerpc64-linux
GCC target triplet: powerpc64-linux
http://sourceware.org/bugzilla/show_bug.cgi?id=6824
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.