similar to: [LLVMdev] Buggy assertion in APFloat::convertFromHexadecimalString

Fixed in r79450, along with an additional one of the same nature. Thanks, - Daniel On Thu, Aug 20, 2009 at 7:42 AM, Enea Zaffanella<zaffanella at cs.unipr.it> wrote: > 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

On Thu, Aug 20, 2009 at 10:13 AM, Daniel Dunbar<daniel at zuster.org> wrote: > Fixed in r79450, along with an additional one of the same nature. > > Thanks, >  - Daniel Thanks Daniel and Enea for finding this! I'm adding a lot more test cases like this to APFloat's unittests so hopefully we won't have any other bugs lying around.

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

Dear R-list, I have a statistical problem with the comparison of two short time-series of density data in an ecological framework. I have to compare two short time series (5 years, one value for each year) of species density data (it is the density of fish in two different streams) to test if the two means of the five densities are significantly different, so basically if the two mean

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

OpenSSL 1.1.0 has deprecated SSL_load_error_strings and SSL_library_init. Initialization is done automatically, so they're not needed with icecast. Fixes issue #2318 Signed-off-by: Eneas U de Queiroz <cote2004-github at yahoo.com> --- src/tls.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/tls.c b/src/tls.c index 36edd86..6bd1aee 100644 --- a/src/tls.c +++ b/src/tls.c @@

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

APFloat is derived from C code using fixed width storage for the matntissa. When converting to C++ I changed it to variable- width storage for space efficiency and generality reasons. Unfortunately this leads to a complication during float->float conversions that I missed that isn't present when using fixed width storage. Dale - I think this solves the issue correctly whilst preserving

Dietmar, > this fixes single precision floating point but breaks double precision. > for arm-softfloat-linux-gnu, FLOAT_WORDS_BIG_ENDIAN is true while > WORDS_BIG_ENDIAN is false. as far as i've seen, there's only a single > flag for endianess in the llvm target description string, so i don't > really understand how this is supposed to work. Hrm, I think I even

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

On Mar 6, 2010, at 3:39 AM, Jochen Wilhelmy wrote: > Hi! > > I wonder if llvm::APFloat::toString() can be const since > it should not modify the APFloat. Done in r97883, thanks.

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

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

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

> 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

On Jul 9, 2010, at 1:20 PMPDT, Jochen Wilhelmy wrote: >> 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

Hi all, What changes to LLVM are needed to support arithmetic for PPCDoubleDouble? arithmeticOK == false for PPCDoubleDouble leads e.g. to assert "Compile-time arithmetic does not support these semantics" when compiling the next function on PowerPC with clang: double quiet_NaN() { return 4.94065645841246544176568792868221e-324L; } -- Regards, Konstantin

On Tue, Jul 24, 2012 at 3:06 AM, Olaf Krzikalla <Olaf.Krzikalla at tu-dresden.de> wrote: > Hi @llvm, > > I stumbled over a strange behavior if a float containing a NaN is printed > (e.g. in the clang rewriter). The local template method "append" in > APFloat.cpp deduces the size from the char array, which for "NaN" is 4 > (including the trailing zero).

Am 24.07.2012 18:50, schrieb David Blaikie: > Do you have a test case to go along with this? Unfortunately not. It just popped up as a result of a programming error made by me. > The simpler fix seems to be to untemplate this code& have "append" > take a StringRef. We can just rely on the compiler to optimize away > the strlen in StringRef's (const char*) ctor as