-
Notifications
You must be signed in to change notification settings - Fork 7
Upgrade Core and Blaze #931
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| vendorpull https://github.com/sourcemeta/vendorpull 1dcbac42809cf87cb5b045106b863e17ad84ba02 | ||
| core https://github.com/sourcemeta/core 036ae97b31bf133fa5c19ad0192bc1eb008f1b0b | ||
| blaze https://github.com/sourcemeta/blaze 31d3723e2bfac22acbaaae23f1f9d02e75ce4c00 | ||
| core https://github.com/sourcemeta/core 3e1d11893f8a7144c4ec2267f5d3f54da551f083 | ||
| blaze https://github.com/sourcemeta/blaze 554ac837d7a088602276df5fff6fac21434fbeda | ||
| bootstrap https://github.com/twbs/bootstrap 1a6fdfae6be09b09eaced8f0e442ca6f7680a61e |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
P2: When a build dir is first configured without a sanitizer and then re-configured with JSONBINPACK_ADDRESS_SANITIZER=ON,
set(... CACHE BOOL ...)without FORCE is a no-op because SOURCEMETA_CORE_USE_SYSTEM_ALLOCATOR is already cached as OFF, so core still links mimalloc (vendor/core/CMakeLists.txt only skips it when this flag AND the sanitizer flags are false). This is a derived value that must track the sanitizer input, so use FORCE so toggling the sanitizer in the same build dir reliably switches core to the system allocator.Prompt for AI agents