Displaying 20 results from an estimated 8000 matches similar to: "[LLVMdev] APFloat.h header file usage"
2007 Dec 08
0
[LLVMdev] APFloat.h header file usage
On Dec 8, 2007, at 1:13 AM, Reid Spencer wrote:
> Hi,
>
> I'm trying to separate the Support, System, ADT and Config header
> files
> into the support module, per previous plans. However, APFloat.h is not
> self-contained:
>
> APFloat.h:105:43: error: llvm/Bitcode/SerializationFwd.h: No such file
> or directory
> APFloat.h:106:37: error:
2007 Dec 08
2
[LLVMdev] APFloat.h header file usage
Hi Ted,
On Sat, 2007-12-08 at 06:59 -0800, Ted Kremenek wrote:
> On Dec 8, 2007, at 1:13 AM, Reid Spencer wrote:
>
> > Hi,
> >
> > I'm trying to separate the Support, System, ADT and Config header
> > files
> > into the support module, per previous plans. However, APFloat.h is not
> > self-contained:
> >
> > APFloat.h:105:43: error:
2007 Dec 08
0
[LLVMdev] APFloat.h header file usage
On Dec 8, 2007, at 11:33 AM, Reid Spencer wrote:
> Okay, but I imagine that leaves it still being used in APFloat.cpp
> which
> is also trying to be segregated to the support module.
>>
>> If this doesn't seem like a clean enough solution, there are other
>> ways to potentially decouple APFloat more from the Serialization
>> "library." The
2015 Aug 10
2
Bug or expected behavior of APFloat class?
Hi,
I've been playing around with the APFloat class lately and I came
across behavior I was not expecting based on reading the
implementation comments and I'm wondering if it's a bug or
intentional.
The behavior concerns converting an APFloat to a string and back
again. In the implementation of ``APFloat::toString(...)`` you can
specify ``FormatPrecision`` as 0. The method comments
2009 Aug 20
3
[LLVMdev] Buggy assertion in APFloat::convertFromHexadecimalString
Hello.
When running clang in Debug mode, I am getting an assertion failure when
parsing the following line:
float ko = 0x1.1p0;
Apparently, the recent changes in the use of StringRef haven't been
propagated to all places. Please find attached the trivial patch.
Cheers,
Enea Zaffanella.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name:
2009 Aug 20
2
[LLVMdev] error api for APInt / APFloat
I'm breaking this out from LLVM asserts thread. Here are all the
assertions in APInt I consider should be recoverable:
APInt::APInt:
bitwidth too small
Null pointer detected!
APInt::getBitsNeeded:
Invalid string length
string is only a minus!
Invalid radix
APInt::fromString:
Radix should be 2, 8, 10, or 16!
Invalid string length
string is only a minus
Insufficient bit width
Invalid digit in
2014 May 15
3
[LLVMdev] 3.4 branch gcc 4.9 build error
On Thu, 15 May 2014 02:25:30 +0200, Tom Stellard wrote:
> On Sat, May 10, 2014 at 11:48:23PM +0200, Tuncer Ayaz wrote:
> > Tom,
> >
> > now that 3.4.1 is out, any chance of a 3.4.2 with just the three
> > fixes or at least merging them to the 3.4 branch?
>
> I've pushed the two approved patches to the 3.4 branch, can you
> verify that they work with gcc
2011 Sep 20
2
[LLVMdev] Clang build "clang-native-arm-cortex-a9" is broken
The host c++ standard library is missing <utility>, it appears.
On Sep 20, 2011, at 11:22 AM, Galina Kistanova wrote:
> Please use the correct link :
> http://63.145.236.72:8011
> and ignore the previous.
>
> Also log for broken build is here:
>
> make[1]: Entering directory
>
2011 Sep 20
0
[LLVMdev] Clang build "clang-native-arm-cortex-a9" is broken
Please use the correct link :
http://63.145.236.72:8011
and ignore the previous.
Also log for broken build is here:
make[1]: Entering directory
`/home/buildslave/zorg/buildbot/osuosl/slave/clang-native-arm-cortex-a9/llvm/lib/Support'
llvm[1]: Compiling APFloat.cpp for Release+Asserts build
llvm[1]: Compiling APInt.cpp for Release+Asserts build
In file included from APFloat.cpp:15:
In file
2014 May 15
2
[LLVMdev] 3.4 branch gcc 4.9 build error
On 15/05/2014 22:12, Tom Stellard wrote:
> On Thu, May 15, 2014 at 01:38:32PM +0200, Tuncer Ayaz wrote:
>> On Thu, 15 May 2014 02:25:30 +0200, Tom Stellard wrote:
>>
>>> On Sat, May 10, 2014 at 11:48:23PM +0200, Tuncer Ayaz wrote:
>>>> Tom,
>>>>
>>>> now that 3.4.1 is out, any chance of a 3.4.2 with just the three
>>>> fixes
2016 Oct 03
2
[PPC, APFloat] Add full PPCDoubleDouble to APFloat
Hi Hal,
On Sun, Oct 2, 2016 at 7:43 PM Hal Finkel <hfinkel at anl.gov> wrote:
> Hi Tim,
>
> How, in general, are you thinking about doing this? I ask because, as you
> clearly know, the double-double format is formed by the sum of two
> double-precision numbers, and the various arithmetic operations are formed
> mostly in terms of double-precision arithmetic on the
2010 Jul 09
2
[LLVMdev] APFloat::convertToDouble asserts
>>
>> 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
2011 Sep 20
1
[LLVMdev] [cfe-commits] Clang build "clang-native-arm-cortex-a9" is broken
Yeah. That code has been there since r91421 and wouldn't have failed recently otherwise. Did something change on the host?
-eric
On Sep 20, 2011, at 11:27 AM, Jim Grosbach wrote:
> The host c++ standard library is missing <utility>, it appears.
>
>
> On Sep 20, 2011, at 11:22 AM, Galina Kistanova wrote:
>
>> Please use the correct link :
>>
2016 Sep 30
2
[PPC, APFloat] Add full PPCDoubleDouble to APFloat
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
2010 Jul 09
0
[LLVMdev] APFloat::convertToDouble asserts
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
2015 Jan 02
2
[LLVMdev] [PATCH] [ADT] APFloat - Fix sign handling for FMA results that truncate to zero.
Hi All,
APFloat::fusedMultiplyAdd currently computes the wrong signed zero when
small negative results are truncated back to zero in standard precision.
The following snippet handles the signedness in fusedMultiplyAdd:
/* If two numbers add (exactly) to zero, IEEE 754 decrees it is a
positive zero unless rounding to minus infinity, except that
adding two like-signed zeroes gives that
2010 Jul 09
2
[LLVMdev] APFloat::convertToDouble asserts
> I'd rather not. The functionality you want is there, feed another
> APFloat type through APFloat::convert first.
>
> Using host FP is not something that should be encouraged; the main
> point of APFloat is so people don't have to do that. Why do you want
> to, btw?
>
Yes, i got it working using APFloat::convert. I need host float to
output to my backend which
2010 Jul 09
0
[LLVMdev] APFloat::convertToDouble asserts
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.
2010 Jul 09
2
[LLVMdev] APFloat::convertToDouble asserts
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
2015 Jan 03
2
[LLVMdev] [PATCH] [ADT] APFloat - Fix sign handling for FMA results that truncate to zero.
Hi Mehdi,
Thanks for the feedback. I think the comment is fine - the problem is just
that the original conditional didn't exactly match it. With the addition of
the underflow check I believe the condition now matches the comment: The
sign is only tweaked if the result of the addition is exactly zero, rather
than a small result that truncates to zero.
CC'ing llvm-commits, where this email