Strip ROM symbols #282
Open
Strip ROM symbols #282
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Quite a few library functions in libgcc.a and libc.a exist in the chip ROM. Previously the duplicate functions in the esp-open-sdk built libgcc were masked by Espressif supplying their own stripped libgcc.a in the SDK, however the functions in the built libc would always have ended up being used over the ROM versions. This would lead to larger and potentially slower code and possibly even memory allocation differences. Since quite a few core string manipulation functions are some of the ones in ROM, this could be significant.
Espressif has recently added an ar script (based on my libgcc script, but with corrected set of object files) into the SDK. This change adds them to the Makefile