-
clspv generally doesn't have support for double-precision floating point. The following at least are missing:
- [x] support double literals (see #157)
- [x] support double constants
- [ ] add supp…
kpet updated
3 months ago
-
https://github.com/Kuratius/sm64/commit/ace0e206ebab999da123168f7ff2dec482f34351
I tried implementing hardware accelerated fdiv and sqrtf functions, I also tried writing an fmul implementation that…
-
**Submitting author:** @goualard-f (Frederic Goualard)
**Repository:** https://github.com/goualard-f/MicroFloatingPoints.jl.git
**Branch with paper.md** (empty if default branch): joss2024
**Version:*…
-
### Motivation / Current Behaviour
We did not consistently use ScalarType for some time, but now we added a FP ("floating point") template parameter to several classes. Instead of fixing inconsistenc…
-
It seems that subnormal floats are not handled by the ROM float routines, and the pico-sdk wrappers don't account for this.
Code to reproduce on pico-sdk 1.5.1 (EDIT: fixed typo where it used to sa…
-
# Feature or enhancement
### Proposal:
The Python supports only decimal floating point literals. But underlying hardware based floating point numbers are binary, not decimal, and conversion to …
-
There is floating point number precision issue in this calculator which is a problem from the JS.
For example: 0.1+0.2=0.30000000000000004
You can round it to 0.3
You can check out this page: https…
-
**'0.5' is not a valid floating point value.**
```
[6DAFC467] System.SysUtils.StrToFloat
[6EA0D4BB] frmGISLongSectionUI.TGISLongSectionForm.btDefineClick (Line 136, "frmGISLongSectionUI.pas")
```
-
**Link:** https://wg21.link/lwg3080
-
### What happens?
DuckDB gives inaccurate result when a decimal is divided by a decimal
### To Reproduce
To reproduce, run below query on DuckDB and Athena. Athena's result matches with the r…