search for: opok

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

I noticed some odd behavior with APFloat's convertFromString method. 1. If I pass the hex representation of the closest value to 0.1 (0x19999Ap-24), everything is fine and opOk is returned. However, if I pass the same value as a decimal string (0.10000002384185791015625), opInexact is set. 2. On the lower end of the scale, the smallest denormal 0x1p-149 returns opOk, but the slightly larger value 0x1.8p-149 has opUnderflow set and (as expected) opInexact. Is this...

Hi Sanjay, Thanks, I saw this flag and it's definitely should be considered, but it appeared to me to be static characteristic of target platform. I'm not sure how appropriate it would be to change its value from a front-end. It says "Has", while optional flag would rather say "Uses" meaning that implementation cares about floating point exceptions. Regards, Sergey

..., 0); } +bool SelectionDAG::isSafeToOptimizeFPOp(APFloat::opStatus s, + APFloat::opStatus UnsafeOps) const { + if (!TLI->hasFloatingPointExceptions()) { + return true; + } + if (getTarget().Options.HonorFPExceptions) { + return s == APFloat::opOK; + } + return (s & UnsafeOps) == APFloat::opOK; +} + SDValue SelectionDAG::getNode(unsigned Opcode, SDLoc DL, EVT VT, SDValue N1, SDValue N2, SDValue N3) { // Perform various simplifications. -- 1.8.4 -------------- next part -------------- Subject: [PATCH...

.../* Re-interpret our bit-pattern. */ exponent += toSemantics.precision - semantics->precision; semantics = &toSemantics; - fs = normalize(rounding_mode, lfExactlyZero); + fs = normalize(rounding_mode, lostFraction); } else { semantics = &toSemantics; fs = opOK;