Commit Graph

15 Commits

Author SHA1 Message Date
Nicolas Brunie bef5a34e1b adding two empty placeholder source file required for RISCV specialization on Linux-x86_64-GCC 2023-10-12 21:07:58 -07:00
Nicolas Brunie 54da0e1be7 Fixing dummy bf16_to_f32 conversion 2023-08-12 10:34:58 +02:00
Nicolas Brunie fab20258f0 Continuing f32_to_bf16 development 2023-08-12 08:00:12 +02:00
Nicolas Brunie ac8688db85 Adding more bf16 support function + skeleton for f32_to_bf16 2023-08-12 06:52:03 +02:00
Nicolas Brunie 3d0376df7b adding initial bf16 support 2023-08-12 04:13:37 +02:00
John Hauser b64af41c32 Fix typo in function 'softfloat_propagateNaNF128M' for RISC-V. 2018-07-26 13:52:23 -07:00
John Hauser f74b1e4811 Release 3e. See "doc/SoftFloat-history.html". 2018-01-26 12:51:15 -08:00
John Hauser db047c521e Release 3d. See "doc/SoftFloat-history.html". 2017-08-10 16:26:24 -07:00
John Hauser 9d731d45e8 Release 3c. See "doc/SoftFloat-history.html". 2017-02-10 12:35:21 -08:00
John Hauser cb5087cd74 Release 3b. See "doc/SoftFloat-history.html". 2016-07-22 18:03:04 -07:00
John Hauser 45fdcf1c65 Added the ability to specify the result values delivered when conversions
from floating-point to an integer format raise an invalid exception.
For the provided specializations (8086 and RISC-V), changed the result
of converting a negative floating-point value to an unsigned integer
format to now be zero.  (Also renamed `shiftCount' inside functions to
`shiftDist'.)
2016-02-22 15:51:12 -08:00
John Hauser 9dc9d10297 For "source/RISCV/specialize.h", updated year in copyright notice to 2016. 2016-01-23 17:56:10 -08:00
Andrew Waterman ab8e0920d5 Employ new RISC-V NaN encoding 2016-01-16 21:22:46 -08:00
John Hauser ad6be28b38 Release 3a. 2015-11-03 14:38:58 -08:00
John Hauser 19c55bae5e Corrected the name of the subdirectory for RISC-V specialization from
"RISC-V" to "RISCV".  (In the names of machines, compilers, targets, etc.,
hyphens are intended for specifying variations and for forming compound
names from multiple such components.  While some arbitrariness in the
application of this rule is inevitable, clearly RISC-V is not a "V"
variation of an existing "RISC" architecture but rather an entirely new
architecture.)
2015-03-12 12:43:06 -07:00