search for: fltsemantics

Hi all, can I access the numeric limits of the llvm types, e.g. HalfTy, FloatTy, DoubleTy, etc. in a fashion like the std numeric_limits tool? std::numeric_limits<half>::min() std::numeric_limits<half>::max() In c++API, I want to initialize values and need to know the correct range for the llvm types.... Thx Alex

This patch supplies software IEEE floating point support. The comment from the patch reproduced below says all there is to say. This patch contains the prior "cleanup" patch; please don't apply that one. Please let me know of any bugs. It is tested reasonably well, but until I put together random tests it's hard to have 100% confidence. Neil. /* A self-contained host- and

...hmetic on the elements of the > pairs. As a result, I suspect we really just want to store the two > double-precision numbers, and essentially delegate to APFloat IEEEdouble in > the implementation of the various operations. > > As such, one option might be that, when PPCDoubleDouble fltSemantics are > selected, the exponent and sign are ignored, and we just store the data for > the two double-precision floating-point numbers in the significand. We > might even do this directly, by making the significand something like this: > > union Significand { > integerPart part...

I have found some internal test failures due to the wrong constant folding on ppc_fp128. As documented in APFloat::PPCDoubleDouble, APFloat doesn't support PowerPC double-double correctly < https://github.com/llvm-mirror/llvm/blob/492acdd450bcdf9837494d6da029ed064f14fc33/lib/Support/APFloat.cpp#L74 >. To support this, we need to add a second tuple of (sign, exponent, significand) to

...literal value (using VisitFloatingLiteral()), it call FloatingLiteral- >getValueAsDouble() and the later does not support long double, so it try to call convertToDouble() as a fallback and crash due to an invalid assertion. APFloat.cpp:2631: failed assertion `semantics == (const llvm::fltSemantics*)&IEEEdouble' This is a know issue as some there is some comments like "// FIXME: We need something for long double here." in FloatingLiteral- >getValueAsDouble(), and "// FIXME: print value more precisely." in VisitFloatingLiteral(). I wonder what will be the...

...sing VisitFloatingLiteral()), it call FloatingLiteral- > >getValueAsDouble() and the later does not support long double, so > it try to call convertToDouble() as a fallback and crash due to an > invalid assertion. APFloat.cpp:2631: failed assertion `semantics == > (const llvm::fltSemantics*)&IEEEdouble' > > This is a know issue as some there is some comments like "// FIXME: > We need something for long double here." in FloatingLiteral- > >getValueAsDouble(), and "// FIXME: print value more precisely." in > VisitFloatingLiteral(). &gt...

...is: assert(category == fcNormal || category == fcNaN); Fibonacci.exe!llvm::APFloat::significandParts() Line 360 + 0x39 bytes C++ Fibonacci.exe!llvm::APFloat::zeroSignificand() Line 387 + 0x15 bytes C++ Fibonacci.exe!llvm::APFloat::APFloat(const llvm::fltSemantics & ourSemantics={...}, unsigned __int64 value=1) Line 307 C++ Fibonacci.exe!`anonymous namespace'::DenseMapAPFloatKeyInfo::getEmptyKey() Line 277 + 0x11 bytes C++ Fibonacci.exe!llvm::DenseMap<`anonymous namespace'::DenseMapAPFloatKeyInfo::KeyTy,llvm::...

...9; to fcNormal before calling significandParts, so I don't see how that assert could be triggered. The call stack looks normal for that source line. It doesn't appear on the Mac. Could your compiler be misoptimizing the code? Fibonacci.exe!llvm::APFloat::APFloat(const llvm::fltSemantics & ourSemantics={...}, unsigned __int64 value=1) Line 307 C++ Fibonacci.exe!`anonymous namespace'::DenseMapAPFloatKeyInfo::getEmptyKey() Line 277 + 0x11 bytes C++ Fibonacci.exe!llvm::DenseMap<`anonymous namespace'::DenseMapAPFloatKeyInfo::KeyTy,llvm...

...e calling significandParts, so I don't see how that assert could be triggered. The call stack looks normal for that source line. It doesn't appear on the Mac. Could your compiler be misoptimizing the code? > Fibonacci.exe!llvm::APFloat::APFloat(const > llvm::fltSemantics & ourSemantics={...}, unsigned __int64 value=1) > Line 307 C++ > > Fibonacci.exe!`anonymous > namespace'::DenseMapAPFloatKeyInfo::getEmptyKey() Line 277 + 0x11 > bytes C++ > > Fibonacci.exe!llvm::DenseMap<`anonymous &gt...

...9; to fcNormal before calling significandParts, so I don't see how that assert could be triggered. The call stack looks normal for that source line. It doesn't appear on the Mac. Could your compiler be misoptimizing the code? Fibonacci.exe!llvm::APFloat::APFloat(const llvm::fltSemantics & ourSemantics={...}, unsigned __int64 value=1) Line 307 C++ Fibonacci.exe!`anonymous namespace'::DenseMapAPFloatKeyInfo::getEmptyKey() Line 277 + 0x11 bytes C++ Fibonacci.exe!llvm::DenseMap<`anonymous namespace'::DenseMapAPFloatKeyInfo::KeyTy,llvm...

...lem case you had? Neil. -------------- next part -------------- Index: lib/Support/APFloat.cpp =================================================================== --- lib/Support/APFloat.cpp (revision 42219) +++ lib/Support/APFloat.cpp (working copy) @@ -1318,39 +1318,44 @@ APFloat::convert(const fltSemantics &toSemantics, roundingMode rounding_mode) { - unsigned int newPartCount; + lostFraction lostFraction; + unsigned int newPartCount, oldPartCount; opStatus fs; - + + lostFraction = lfExactlyZero; newPartCount = partCountForBits(toSemantics.precision + 1); + oldPartCount = partCo...

...Signals.cpp for Release build llvm[1]: Compiling TimeValue.cpp for Release build llvm[1]: Compiling ltdl.c for Release build llvm[1]: Building Release Archive Library libLLVMSystem.a llvm[1]: Compiling APFloat.cpp for Release build APFloat.cpp: In constructor 'llvm::APFloat::APFloat(const llvm::fltSemantics&, const char*)': APFloat.cpp:680: warning: control may reach end of non-void function 'llvm::APFloat::opStatus llvm::APFloat::convertFromString(const char*, llvm::APFloat::roundingMode)' being inlined llvm[1]: Compiling APInt.cpp for Release build llvm[1]: Compiling Allocator.cpp fo...

..., so I don't see how that assert > could be triggered. The call stack looks normal for that source > line. It doesn't appear on the Mac. Could your compiler be > misoptimizing the code? > >> Fibonacci.exe!llvm::APFloat::APFloat(const >> llvm::fltSemantics & ourSemantics={...}, unsigned __int64 >> value=1) Line 307 C++ >> >> Fibonacci.exe!`anonymous >> namespace'::DenseMapAPFloatKeyInfo::getEmptyKey() Line 277 + 0x11 >> bytes C++ >> >> Fibonacci.exe!llvm::...