| Age | Commit message (Collapse) | Author |
|
This was broken both in comptime code and in runtime code.
closes #1174
|
|
fixes float literals not having 128 bit precision
|
|
Add support for half-precision floating point operations.
Introduce `__extendhfsf2` and `__truncsfhf2` in std/special/compiler_rt.
Add `__gnu_h2f_ieee` and `__gnu_f2h_ieee` as aliases that are used in
Windows builds.
The logic in std/special/compiler_rt/extendXfYf2.zig has been reworked
and can now operate on 16 bits floating point types.
`extendXfYf2()` and `truncXfYf2()` are marked `inline` to work around
a not entirely understood stack alignment issue on Windows when calling
the f16 versions of the builtins.
closes #1122
|
|
See #767
|
|
See #302
See #467
|
|
previously we used the bigfloat abstraction to do all
compile-time float math. but runtime code and comptime code
are supposed to get the same result. so now if you add a
f32 to a f32 at compile time it does it with f32 math
instead of the bigfloat. float literals still get the
bigfloat math.
closes #424
|
|
|
|
it seems to be shipped with gcc and clang
|
|
|
|
|
|
and make bigfloat use __float128
|
|
closes #414
|
|
|