wasm32-unknown-unknown: Fix undefined malloc/free/calloc symbols (#275) #2
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.
As discussed in gyscos#250, in some cases the definitions of
malloc
,free
, andcalloc
are used but don't get linked in, leading to undefined symbols (i.e. reference to the symbol in "env").I was not able to determine exactly why this is happening, but it seems to be related to
malloc
,calloc
, andfree
being defined as inline functions. When building in debug mode there are undefined symbols; when building in release mode there are not, presumably because the functions are inlined.Switching to macros avoids issues of inlining and fixes this issue for me.