Skip to content

Unify and fix approaches in dtoa & strtod #843

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

Open
MaxGraey opened this issue Sep 15, 2019 · 5 comments
Open

Unify and fix approaches in dtoa & strtod #843

MaxGraey opened this issue Sep 15, 2019 · 5 comments

Comments

@MaxGraey
Copy link
Member

We have some misprisions and failed tests for #768 and mentioned in #337. dtoa and strtod should utilize same big float point math which could be shared. Refactor and fix this

@MaxGraey MaxGraey self-assigned this Sep 15, 2019
@MaxGraey
Copy link
Member Author

MaxGraey commented Oct 9, 2019

Currently we use Grisu2 algorithm which precise in 99.5% cases and require fallback to Dragon4 algorithm for rest of cases. I guess better investigate time to new Ryū algorithm which faster and always precise but require 10kb lookup table which possible avoid for shrinked >= 1 optimization cases

@MaxGraey
Copy link
Member Author

MaxGraey commented Oct 18, 2019

Also new great paper about father research Ryu alghoritm and integrate it to printf

@dcodeIO
Copy link
Member

dcodeIO commented May 28, 2020

@MaxGraey Do you think #337 can be merged into this one?

@MaxGraey
Copy link
Member Author

yes, sure

@MaxGraey
Copy link
Member Author

Instead Ryu we could implement more novel and faster Schubfach algorithm:
https://drive.google.com/file/d/1luHhyQF9zKlM8yJ1nebU0OgVYhfC6CBN/view

or Dragonbox:
https://github.com/abolz/Drachennest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants