-
Notifications
You must be signed in to change notification settings - Fork 63
Fixes #84: Choice of float/double
#116
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
Conversation
e91b7e5 to
e0ef6ca
Compare
|
I think it looks good so far.
I can try it out on microcontroller on the weekend. |
It shouldn't! If that happens, I have a bug. I tried to support double = 32-bits even when
One step at a time :-) ... also, I've created v6.0.0 with my recent changes. Would appreciate feedback there as well. |
I misread the code, I think you are right. |
|
Just so you know, though, I'm not hurrying to merge this before I get some feedback of the v6.0.0 pre-release; and properly release it. Then this can go on the development branch. |
52e9999 to
2b85ce1
Compare
* Can now choose between using `double` and `float` internally, for floating-point work, using the `PRINTF_USE_DOUBLE_INTERNALLY` definition and corresponding CMake option. * Adjusted test suite to support the different choice of floating-point type: * Tests relevant both to `float` and `double`, but with different precisions, are adjusted with an `#if #else #endif` * Tests and test cases relevant only for `double` precision are not compiled at all when `float` is used. * Lots of new explicit conversions :-(
|
Hello, I see this was merged into develop. I personally tried this new option on a Cortex M4 with FP unit and it reduced code size by around 800 bytes, so that is good. Also my program still works fine. Thanks for the work, just thought I would give a testimony to the fact this works hehe. |
|
Thank you, @crazybolillo , it's nice to get positive feedback :-) |
Fixes #84.