chore(deps): update mimalloc3 submodule to v3.4.3 - #91
Open
Nic-Polumeyv wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
1 participant
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.
Advances the mimalloc3 submodule from d7d90c6 (v3.3.2-33) to the v3.4.3 tag, a fast-forward. Closes #90.
Besides the security fixes #90 asks for, this picks up the POPCNT guard from microsoft/mimalloc#1291 (downstream report: rolldown/rolldown#10457).
Ran the ci.yml cargo matrix locally on Linux x64 (default, secure, extended, v3, extended+v3, plus libmimalloc-sys-test under each), all passing. All cmake options build.rs defines still exist in v3.4.3, including MI_TLS_MODEL_LOCAL and MI_TLS_RECURSE_GUARD; the upstream macOS TLS-slot revert in v3.4.x (microsoft/mimalloc#1333) doesn't apply here since build.rs forces the local TLS model.