Displaying 10 results from an estimated 10 matches for "754r".
Did you mean:
754
2013 Jun 18
4
[LLVMdev] APFloat renaming isNormal => isFiniteNonZero and isIEEENormal => isNormal
IEEE-754R defines a normal floating point number as:
2.1.38 normal number: For a particular format, a finite non-zero floating-point number with magnitude greater than or equal to a minimum bemin value, where b is the radix. Normal numbers can use the full precision available in a format. In this standard, z...
2013 Jun 19
0
[LLVMdev] APFloat renaming isNormal => isFiniteNonZero and isIEEENormal => isNormal
LGTM (and you've already gotten other positive feedback as well).
-eric
On Tue, Jun 18, 2013 at 3:45 PM, Michael Gottesman <mgottesman at apple.com> wrote:
> IEEE-754R defines a normal floating point number as:
>
> 2.1.38 normal number: For a particular format, a finite non-zero
> floating-point number with magnitude greater than or equal to a minimum
> bemin value, where b is the radix. Normal numbers can use the full precision
> available in a fo...
2013 Jun 18
0
[LLVMdev] APFloat renaming isNormal => isFiniteNonZero and isIEEENormal => isNormal
I think it’s a splendid idea (but you already knew that).
On Jun 18, 2013, at 6:45 PM, Michael Gottesman <mgottesman at apple.com> wrote:
> IEEE-754R defines a normal floating point number as:
> 2.1.38 normal number: For a particular format, a finite non-zero floating-point number with magnitude greater than or equal to a minimum bemin value, where b is the radix. Normal numbers can use the full precision available in a format. In this standa...
2013 Jun 19
1
[LLVMdev] APFloat renaming isNormal => isFiniteNonZero and isIEEENormal => isNormal
...Michael
On Jun 18, 2013, at 5:07 PM, Eric Christopher <echristo at gmail.com> wrote:
> LGTM (and you've already gotten other positive feedback as well).
>
> -eric
>
> On Tue, Jun 18, 2013 at 3:45 PM, Michael Gottesman <mgottesman at apple.com> wrote:
>> IEEE-754R defines a normal floating point number as:
>>
>> 2.1.38 normal number: For a particular format, a finite non-zero
>> floating-point number with magnitude greater than or equal to a minimum
>> bemin value, where b is the radix. Normal numbers can use the full precision
>&...
2007 Mar 22
0
[LLVMdev] a question about constant fold for fdiv
...icitly handle 0/0, but the
> position of the IEEE appears to be that it should yield a NaN of the
> appropriate sign. See
> http://standards.ieee.org/reading/ieee/interp/754-1985.html
OK, it does explicitly handle it. My reading comprehension seems to be
lacking right now :(
http://754r.ucbtest.org/standards/754xml.html#invalid-exception
The above lists all operations that yield a NaN.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070322/eedc80e2/attachment.html>
2007 Mar 22
2
[LLVMdev] a question about constant fold for fdiv
Jeff Cohen wrote:
> Jeff Cohen wrote:
>> Reid Spencer wrote:
>>> On Thu, 2007-03-22 at 15:50 -0700, leo han wrote:
>>>
>>>> Hello, I have a question about the constant folding for fdiv instructions.
>>>> For the instruction "fdiv double 0.0, 0.0", the folded result is inf. I
>>>> think this should be nan. Can anyone tell
2015 Jan 22
4
[LLVMdev] FYI: IA-32 psABI draft version 0.1
Here is the link:
https://groups.google.com/forum/#!topic/ia32-abi/nq6cvH_VVV4
--
H.J.
2015 Jan 22
0
[LLVMdev] FYI: IA-32 psABI draft version 0.1
...it back from the list - you might want to check if it's stuck in
moderation somewhere:
I would suggest that rather than using old terms such as "single",
"double" and "128-bit extended" to describe floating-point formats, and
rather than referring to "IEEE-754R", the names from IEEE 754-2008 should
be used. That is, binary32, binary64, binary128. (When referring to
decimal32, decimal64, decimal128 you still need to specify somewhere that
it's BID rather than DPD. And you'll still need to refer to 80-bit
extended since that's not an...
2007 Aug 18
1
[LLVMdev] Soft floating point support
...rithmetic can be correctly performed on the host. Performance
should nonetheless be reasonable, particularly for its intended
use. It may be useful as a base implementation for a run-time
library during development of a faster target-specific one.
All 5 rounding modes in the IEEE-754R draft are handled correctly
for all implemented operations. Currently implemented operations
are add, subtract, multiply, divide, fused-multiply-add,
conversion-to-float, conversion-to-integer and
conversion-from-integer. New rounding modes (e.g. away from zero)
can be added w...
2017 Jun 21
6
RFC: Cleaning up the Itanium demangler
...# __int128
// ::= o # unsigned __int128
// ::= f # float
// ::= d # double
// ::= e # long double, __float80
// ::= g # __float128
// ::= z # ellipsis
// ::= Dd # IEEE 754r decimal floating point (64 bits)
// ::= De # IEEE 754r decimal floating point (128 bits)
// ::= Df # IEEE 754r decimal floating point (32 bits)
// ::= Dh # IEEE 754r half-precision floating point (16 bits)
// ::= Di # char32_t...