search for: ieee754

On a system with IEEE_754 undefined, I run into an bug, when the value of an element of the first argument (e.g., x[0]) of formatReal() is NA: 1. (format.c:235) if (!R_FINITE ..) gives nanflag=1 (!naflag remains 0) 2. (format.c:272..288) *m gets an value of -2147483643 (from the format fiddling, should not matter to us) 3. (format.c:289) because naflag is zero, m does not

...t test-suite runs since we can just update the assembler but is causing trouble for microMIPS. More recent toolchains lack the microMIPS multilib I was using and migrating to the new one is causing link failures. These failures are related to ELF header bits specifying the SNaN/QNaN encodings to be IEEE754-1985 or IEEE754-2008 compliant. I suspect the -mnan=2008 isn't reaching the assembler. 3. Clang is incompatible with changes to the mips-mti-linux-gnu sysroot from Imagination's mips-mti-linux-gnu toolchain. Libaries are still multilib'd (albeit with a reduced set) but some of th...

Hi, I'd like to make code emitted by LLVM that includes floating point operations which raise FP exceptions behave closer to what is defined by IEEE754 standard. I'm not going to "fix everything", just incorrect behaviour I faced so far. Most of troubles regarding FP exceptions are caused by optimizations, so there should be a flag to disable/block them if one wants to get better code in a sense of its IEEE754 conformance. I could...

R is having trouble finding some of the things it needs to compile. In particular, I'm getting messages saying that it can't find things it wants in -lblas, -ldxml, -ldnet, and -ldnet_stub. It also can't find dl.h, ieeefp.h, and ieee754.h. I can't figure out whether these things are included with R somewhere and I need to tell it where to look, or they're not included and I need to get them. I also can't figure out where I would set the -lblas, -ldxml variables. I've looked through make files and configure files...

...FMA intrinsics aggressively, but in order to do so I need some clarification on the intended semantics for the various FP precision-related TargetOptions. I've summarized the three relevant ones below: UnsafeFPMath - Defaults to off, enables "less precise" results than permitted by IEEE754. Comments specifically reference using hardware FSIN/FCOS on X86. NoExcessFPPrecision - Defaults to off (i.e. excess precision allowed), enables higher-precision implementations than specified by IEEE754. Comments reference FMA-like operations, and X87 without rounding all over the place. LessP...

...s at imgtec.com<mailto:Daniel.Sanders at imgtec.com>> wrote: > I am not entirely sure this is safe. Transforming this to an fsub could change the value stored on platforms that implement negates using arithmetic instead of with bitmath (such as ours) I think it's probably safe for IEEE754-2008 conformant platforms because negation was clarified to be a non-arithmetic bit flip that cannot cause exceptions in that specification. I did some digging into IEEE-754 and it seems like this is actually not even safe on fully conformant IEEE-754-2008 platforms. 5.5.1 Sign bit operations 5.5...

...nce we can just update the > assembler but is causing trouble for microMIPS. More recent toolchains lack > the microMIPS multilib I was using and migrating to the new one is causing > link failures. These failures are related to ELF header bits specifying the > SNaN/QNaN encodings to be IEEE754-1985 or IEEE754-2008 compliant. I suspect > the –mnan=2008 isn't reaching the assembler. > > 3. Clang is incompatible with changes to the mips-mti-linux-gnu > sysroot from Imagination's mips-mti-linux-gnu toolchain. Libaries are still > multilib'd (albeit with a red...

> I am not entirely sure this is safe. Transforming this to an fsub could change the value stored on platforms that implement negates using arithmetic instead of with bitmath (such as ours) I think it's probably safe for IEEE754-2008 conformant platforms because negation was clarified to be a non-arithmetic bit flip that cannot cause exceptions in that specification. However, I'm sure it's unsafe for some IEEE754-1985 platforms because it introduces exceptions when given a NaN. On MIPS, the semantics for negation...

...Tue, Oct 8, 2019 at 7:08 AM Szabolcs Nagy <nsz at port70.net> wrote: > > why is that ok? > > > > Because there are no FP exceptions/signals for this IR opcode: > http://llvm.org/docs/LangRef.html#floating-point-environment so llvm cannot support an iso c frontend on an ieee754 target? (or fortran for that matter)

If fptosi takes 0.9 -> 0, then that is not 'rounding' in any sense I'm aware of (IEEE754 or otherwise). Rounding (in the IEE754 sense) determines how a number is converted when it is halfway between two candidate results. (see round(), ceil(), floor()). fptosi seems to model the behavior of a C cast from float to int, which truncates the fractional bits (as in trunc()). Steve On F...

...t test-suite runs since we can just update the assembler but is causing trouble for microMIPS. More recent toolchains lack the microMIPS multilib I was using and migrating to the new one is causing link failures. These failures are related to ELF header bits specifying the SNaN/QNaN encodings to be IEEE754-1985 or IEEE754-2008 compliant. I suspect the –mnan=2008 isn't reaching the assembler. 3. Clang is incompatible with changes to the mips-mti-linux-gnu sysroot from Imagination's mips-mti-linux-gnu toolchain. Libaries are still multilib'd (albeit with a reduced set) but some of th...

...e > > assembler but is causing trouble for microMIPS. More recent toolchains > lack > > the microMIPS multilib I was using and migrating to the new one is causing > > link failures. These failures are related to ELF header bits specifying the > > SNaN/QNaN encodings to be IEEE754-1985 or IEEE754-2008 compliant. I > suspect > > the –mnan=2008 isn't reaching the assembler. > > > > 3. Clang is incompatible with changes to the mips-mti-linux-gnu > > sysroot from Imagination's mips-mti-linux-gnu toolchain. Libaries are still > > mul...

...ion was successful but make check fails. I traced the the problem to the plot() function. > 1 + 1 [1] 2 > capabilities() jpeg png tcltk X11 GNOME libz http/ftp sockets TRUE FALSE TRUE TRUE FALSE TRUE TRUE TRUE libxml fifo cledit IEEE754 bzip2 PCRE TRUE TRUE TRUE TRUE TRUE TRUE > plot( 1:10 ) Bus Error and R terminates to the shell prompt. I have searched the archives with no success. Can anyone kindly help me fix the problem or at least show me how to get more information about the error. Thank...

...o configure:12433: $? = 0 configure:12443: result: yes configure:12447: checking grp.h presence configure:12458: gcc -E -I/usr/local/include conftest.c configure:12464: $? = 0 configure:12483: result: yes configure:12519: checking for grp.h configure:12526: result: yes configure:12411: checking ieee754.h usability configure:12424: gcc -c -m64 -g -02 -I/usr/local/include conftest.c >&5 gcc: unrecognized option `-02' configure:12488:21: ieee754.h: No such file or directory configure:12427: $? = 1 configure: failed program was: | #line 12413 "configure" | /* confdefs.h. */ |...

...FMA intrinsics aggressively, but in order to do so I need some clarification on the intended semantics for the various FP precision-related TargetOptions. I've summarized the three relevant ones below: UnsafeFPMath - Defaults to off, enables "less precise" results than permitted by IEEE754. Comments specifically reference using hardware FSIN/FCOS on X86. NoExcessFPPrecision - Defaults to off (i.e. excess precision allowed), enables higher-precision implementations than specified by IEEE754. Comments reference FMA-like operations, and X87 without rounding all over the place. LessP...

.... checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no . . . checking floatingpoint.h usability... no checking floatingpoint.h presence... no checking for floatingpoint.h... no . . . checking ieee754.h usability... yes checking ieee754.h presence... yes checking for ieee754.h... yes checking ieeefp.h usability... no checking ieeefp.h presence... no checking for ieeefp.h... no . . . checking for dummy main to link with Fortran libraries... none . . . checking whether isfinite is declare...

On Jan 14, 2009, at 5:11 AM, Syoyo Fujita wrote: > Thanks for many comments. > > The loop with finite fp values(which could be representable in IEEE754 > fp format) such like, Sure, LLVM could definitely do this. If you're interested, I'd suggest starting by extending the existing code that we have to do this. The existing code just handles increments by unit constants, so it doesn't trigger with 1.2. -Chris

...n linux. The issue is that a raw > call to sqrt() in a C program doesn't typically compile to llvm.sqrt > on linux, because it sets errno. This can be controlled with -fmath- > errno. It is more than errno. sqrt() should't compile to llvm.sqrt on any platform that uses IEEE754 math, because IEEE sqrt() is well defined on negative arguments and llvm.sqrt isn't. There are currently no command line arguments to override this.

...abilities()", and it displayed indentical results to the "right" ones described in your letter, that is: "> capabilities() jpeg png tcltk X11 http/ftp sockets libxml fifo TRUE TRUE TRUE TRUE TRUE TRUE TRUE TRUE cledit IEEE754 iconv TRUE TRUE TRUE" And I can not pass the "make check" all the same. Is there any other possible reasons which could cause this depressing problem? Thanks! Sincerely yours,...

...t test-suite runs since we can just update the assembler but is causing trouble for microMIPS. More recent toolchains lack the microMIPS multilib I was using and migrating to the new one is causing link failures. These failures are related to ELF header bits specifying the SNaN/QNaN encodings to be IEEE754-1985 or IEEE754-2008 compliant. I suspect the –mnan=2008 isn't reaching the assembler. > > 3. Clang is incompatible with changes to the mips-mti-linux-gnu sysroot from Imagination's mips-mti-linux-gnu toolchain. Libaries are still multilib'd (albeit with a reduced set) but...