-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lookup tables and binary size difference #1
Comments
Note that the other fairly large user of memory here is the Decimal type. This uses 768 bytes for the digits storage. This space seems reasonable too me, but note that f128 parsing requires a lot more. Specifically the Decimal requires 11563 bytes for storage if parsing to an f128 with full precision. I have yet to fully explore actually using eisel-lemire for f128 parsing but my first revision will likely use the slow-path algorithm only initially.
So, a bit larger. |
There is also this table I forgot about: Line 306 in 1ea6a9a
|
btw we have the
|
// Eisel-Lemire tables ~10Kb
, so I am curious how much space float parsing for embedded would require in contrast to that.The text was updated successfully, but these errors were encountered: