Fix two compiler warnings in memory.c
#5023
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.
First warning:
The use of
volatile
fornewmemstruct
seems on purpose, and there are more such constructs in this file. The warning appeared after gh-4451 and is correct. Thefree
prototype doesn't expect a volatile pointer, hence this change adds a cast to silence the warning.Second warning:
The added define is the same as is already present in the TLS part of
memory.c
. This follows up on gh-4681.