[LLVMbugs] [Bug 11111] New: clang 2.9 and svn miscompiles MPFR 3.1.0
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Tue Oct 11 09:00:25 PDT 2011
http://llvm.org/bugs/show_bug.cgi?id=11111
Summary: clang 2.9 and svn miscompiles MPFR 3.1.0
Product: clang
Version: trunk
Platform: Macintosh
OS/Version: All
Status: NEW
Severity: normal
Priority: P
Component: -New Bugs
AssignedTo: unassignedclangbugs at nondot.org
ReportedBy: howarth at nitro.med.uc.edu
CC: llvmbugs at cs.uiuc.edu
The clang compilers from both the 2.9 release and current svn both miscompile
the MPFR 3.1.0 library. The resulting binaries on x86_64-apple-darwin11 fail
their testsuite with...
[tversion] GMP: header 5.0.2, library 5.0.2
[tversion] MPFR tuning parameters from src/x86_64/core2/mparam.h
PASS: tversion
PASS: tinternals
PASS: tinits
PASS: tisqrt
PASS: tsgn
PASS: tcheck
PASS: tisnan
Error: emin >= emax
FAIL: texceptions
../../tests/tset_exp.c:44: MPFR assertion failed: ret == 0 &&
(__builtin_constant_p (2) && (mpfr_ulong) (2) == 0 ? (mpfr_sgn) (x) :
mpfr_cmp_ui_2exp ((x), (2), 0)) == 0
/bin/sh: line 1: 68248 Abort trap: 6 MPFR_QUIET=1 ${dir}$tst
FAIL: tset_exp
/bin/sh: line 1: 68267 Segmentation fault: 11 MPFR_QUIET=1 ${dir}$tst
FAIL: tset
PASS: mpf_compat
Error in conversion to/from mpz
expected 17, got 0.0000000000000000e+00
FAIL: mpfr_compat
../../src/set_str_raw.c:54: MPFR assertion failed: res == 0
/bin/sh: line 1: 68319 Abort trap: 6 MPFR_QUIET=1 ${dir}$tst
FAIL: reuse
/bin/sh: line 1: 68337 Segmentation fault: 11 MPFR_QUIET=1 ${dir}$tst
FAIL: tabs
This problem doesn't exist in Apple's Xcode 4.1.1 release but apparently exists
in Xcode 4.2 now.
These failures are suppressed if MPFR is passed --disable-thread-safe.
Comparing the config.log generated against Apple's clang from Xcode 4.1 and
llvm.org's 2.9 clang, I see...
-checking for TLS support... no
+checking for TLS support... yes
suggesting that the TLS support in clang svn is buggy.
--
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the llvm-bugs
mailing list