search for: ieeedouble

Hi! I wonder why APFloat::convertToDouble asserts if it is not an APFloat::IEEEdouble while the name "convertToDouble" suggests that it converts when it is not a double. -Jochen

...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(). I wonder what will be the best way to solv...

...iteral()), 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 w...

On Jul 9, 2010, at 7:59 AMPDT, Jochen Wilhelmy wrote: > Hi! > > I wonder why APFloat::convertToDouble asserts if it is not an > APFloat::IEEEdouble while the name "convertToDouble" suggests that it > converts when it is not a double. The conversion is to (host) double, as the name implies. Among APFloat types, that is only implemented for APFloat::IEEEdouble.

>> >> I wonder why APFloat::convertToDouble asserts if it is not an >> APFloat::IEEEdouble while the name "convertToDouble" suggests that it >> converts when it is not a double. > > The conversion is to (host) double, as the name implies. Among > APFloat types, that is only implemented for APFloat::IEEEdouble. > yes, it's to host double ("convert t...

...lvm/clang-3.0rc3.src/unittests/AST/APValueTest.cpp:63: Failure Value of: GetDiagnosticOutput(APValue(APSInt(APInt(16, 5)))) Actual: "" Expected: "5" /home/jay/llvm/clang-3.0rc3.src/unittests/AST/APValueTest.cpp:66: Failure Value of: GetDiagnosticOutput(APValue(APFloat(APFloat::IEEEdouble, "3.14159"))) Actual: "" Expected: "3.141590e+00" /home/jay/llvm/clang-3.0rc3.src/unittests/AST/APValueTest.cpp:69: Failure Value of: GetDiagnosticOutput(APValue(APSInt(APInt(16, 3)), APSInt(APInt(16, 4)))) Actual: "" Expected: "3+4i" /home/jay/...

Good day, LLVMers! We are starting on our third (and hopefully last) round of testing for LLVM 3.0. Please visit: http://llvm.org/pre-releases/3.0/rc3/ for the sources. There are also binaries for Darwin up there, with more to come during the week. Please build this release candidate, test it out on your projects, and let us know if you find any regressions from the 2.9 release. Please keep

...ttests/AST/APValueTest.cpp:63: Failure > Value of: GetDiagnosticOutput(APValue(APSInt(APInt(16, 5)))) > Actual: "" > Expected: "5" > /home/jay/llvm/clang-3.0rc3.src/unittests/AST/APValueTest.cpp:66: Failure > Value of: GetDiagnosticOutput(APValue(APFloat(APFloat::IEEEdouble, "3.14159"))) > Actual: "" > Expected: "3.141590e+00" > /home/jay/llvm/clang-3.0rc3.src/unittests/AST/APValueTest.cpp:69: Failure > Value of: GetDiagnosticOutput(APValue(APSInt(APInt(16, 3)), > APSInt(APInt(16, 4)))) > Actual: "" > Expe...

On Jul 9, 2010, at 12:59 PMPDT, Jochen Wilhelmy wrote: >>> I wonder why APFloat::convertToDouble asserts if it is not an >>> APFloat::IEEEdouble while the name "convertToDouble" suggests that >>> it >>> converts when it is not a double. >> >> The conversion is to (host) double, as the name implies. Among >> APFloat types, that is only implemented for APFloat::IEEEdouble. >> > >...

...isHalf" variable in that spot. (line > 720) I'm not sure I get it. This variable is still needed couple of lines below: bool isHalf = &CFP->getValueAPF().getSemantics()==&APFloat::IEEEhalf; bool isDouble = &CFP->getValueAPF().getSemantics()==&APFloat::IEEEdouble; bool isInf = CFP->getValueAPF().isInfinity(); bool isNaN = CFP->getValueAPF().isNaN(); if (!isHalf && !isInf && !isNaN) { > // Either half, or some form of long double. > // These appear as a magic letter identifying the type, then a >...

...> > 720) > I'm not sure I get it. This variable is still needed couple of lines > below: > > bool isHalf = &CFP- > >getValueAPF().getSemantics()==&APFloat::IEEEhalf; > bool isDouble = > &CFP->getValueAPF().getSemantics()==&APFloat::IEEEdouble; > bool isInf = CFP->getValueAPF().isInfinity(); > bool isNaN = CFP->getValueAPF().isNaN(); > if (!isHalf && !isInf && !isNaN) { > > > // Either half, or some form of long double. > > // These appear as a magic letter identify...

I've got comments on the code change. The test cases look ok, but I haven't fully checked the math on the half-values. I checked with reference to trunk top-of-tree at revision 156617. I have not compiled the code. lib/AsmParser/LLLexer.cpp Adds support to parse format: 0xH<hexdigits> Tha 0xH format should be described in LangRef.html alongside 0xK<hex> and

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

...f two > double-precision numbers, and the various arithmetic operations are formed > mostly in terms of double-precision arithmetic 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 >...

...not sure I get it. This variable is still needed couple of lines > > below: > > > > bool isHalf = &CFP- > > >getValueAPF().getSemantics()==&APFloat::IEEEhalf; > > bool isDouble = > > &CFP->getValueAPF().getSemantics()==&APFloat::IEEEdouble; > > bool isInf = CFP->getValueAPF().isInfinity(); > > bool isNaN = CFP->getValueAPF().isNaN(); > > if (!isHalf && !isInf && !isNaN) { > > > > > // Either half, or some form of long double. > > > // These appe...

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

...e.write((char*)&Hdr, sizeof(Hdr)); Index: lib/Target/CBackend/CBackend.cpp =================================================================== --- lib/Target/CBackend/CBackend.cpp (revision 117247) +++ lib/Target/CBackend/CBackend.cpp (working copy) @@ -746,7 +746,7 @@ APF.convert(APFloat::IEEEdouble, APFloat::rmNearestTiesToEven, &ignored); #if HAVE_PRINTF_A && ENABLE_CBE_PRINTF_A char Buffer[100]; - sprintf(Buffer, "%a", APF.convertToDouble()); + snprintf(Buffer, sizeof(Buffer), "%a", APF.convertToDouble()); if (!strncmp(Buffer, "0x", 2) ||...

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