Crates.io | nanval |
lib.rs | nanval |
version | 0.2.1 |
source | src |
created_at | 2021-12-12 19:23:20.264712 |
updated_at | 2022-11-15 16:59:19.23751 |
description | A no_std, zero-dependency crate for the creation and handling of NaN-tagged 64-bit floating-point values. |
homepage | https://github.com/Longor1996/nanval |
repository | https://github.com/Longor1996/nanval |
max_upload_size | |
id | 496684 |
size | 26,513 |
A no_std
, zero-dependency crate for the creation and handling of NaN-tagged 64-bit floating-point values.
Inspired by this article and this crate.
When a 64-bit floating-point number is set to NaN
/0x7FF8000000000000
, its bits are as follows:
s111 1111 1111 1qxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
^ ^\____________________________________________________________/
| | ^
| Sign Bit | Quiet Bit | Data Bits
As long as the data bits aren't all set to 0
, indicating the original/sentinel NaN
value, they can be literally anything else! This gives us 50 bits to mess with/use as we please...
Look at the module [
crate::uint
] for this.
TODO: Add explanation.
Look at the module [
crate::cell
] for this.
Since it doesn't matter what the sign-bit s
is set to, we can use it as a flag/marker that indicates that the value is some kind of cell
or ptr
.
Combine this with the fact that basically all x64-platforms only use the lower 48 or 50 bits for addressing (ignoring CHERI shenanigans), we are left with 3 bits (that includes the 'quiet' bit) to store some kind of type-tag for the cell; look at the [crate::cell::CellTag
].