Displaying 4 results from an estimated 4 matches for "1.0e0".
Did you mean:
1.00
2011 Apr 24
2
random roundoff?
On my CentOS 5 box, in a C++ program that does much arithmetic,
including numerous matrix multiplications, I have a situation in
in which the result depends on the nature of nearby I/O. Thus,
with all arithmetic done with type double, and where values
are mostly in the range [-1.0e0,+1.0e0] or nearby, I do:
cerr << "some stuff" << endl;
mat3 = matmult(mat1,mat2);
I
2024 Feb 06
2
Advice debugging M1Mac check errors
On 04/02/2024 19:41, Holger Hoefling wrote:
> Hi,
>
> I wanted to ask if people have good advice on how to debug M1Mac package
> check errors when you don?t have a Mac? Is a cloud machine the best option
> or is there something else?
I presumed this was about a CRAN package, possibly hdf5r which has a
R-devel-only warning from the Apple clang compiler. And that is not a
2019 Apr 11
2
128 bit float constant
Hi Tim,
Thanks for the hint.
I tried the following, (it's a C interface since that's what I need it for)
where a and b are
the top and bottom halves of the 128 bit value,
LLVMValueRef TestConst(LLVMContextRef C, uint64_t a, uint64_t b) {
Type *ty = Type::getFP128Ty(*unwrap(C));
ArrayRef<uint64_t> ar[2] = {a,b};
APInt ai(128,*ar);
APFloat quad(APFloat::IEEEquad(), ai);
2019 Apr 10
2
128 bit float constant
Hi,
Just wondering if it's possible to construct a 128 bit quad precision
floating point
constant without converting the value back to a string.
Cheers Peter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190410/a527f240/attachment.html>