Move floating point from libgcc out of IRAM #7180
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Tasmota I realized the following floating point function are in precious IRAM:
This PR adds a
#define FP_IN_IROM
to move floating point function out of IRAM to IROM.*f2.o
,*f3.o
:float
anddouble
functions*fsi.o
: fp to int*fdi.o
: fp to long*ifs.o
: int to fp*ids.o
: long to fpIn Tasmota, the only functions from
libgcc
remaining in IRAM are:__modsi3
(integer modulus) and__ashrdi3
(bit shifting).The net result is reducing IRAM usage by 1040 bytes.