Always use size_t in dlmalloc's mallinfo
#23368
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.
For some reason emscripten was overriding
MALLINFO_FIELD_TYPEto beinteven though this defaultssize_tandsize_tis what linux uses, andsize_tallows for correct reporting of numbers larger than 2^32.What is worse, the
MALLINFO_FIELD_TYPEoverride was only applied whenDLMALLOC_DEBUGwas defined which meant thatMALLINFO_FIELD_TYPEvaried between-sASSERTIONS=1and-sASSERTIONS=2builds of dlmalloc!This means that
-sMEMORY64 + -sASSERTIONS=2builds of dlmalloc were simply broken WRTmallinfosince the public definition of mallinfo disagreed with the dlmalloc-internal version.I verified that the follow tests fails without this change:
EMCC_CFLAGS=-sASSERTIONS=2 ./test/runner wasm64.test_mallinfoI'm not updating the actual test code here since test coverage will be coming in #23330.
This change was spit out from #23330.