[🍒][SwiftCore]: Don't always clobber memory #81040
Merged
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
The new build system set `SWIFT_RUNTIME_CLOBBER_FREED_OBJECTS` to 0. Unfortunately, the check in the Swift runtime used `#ifdef`, so even though it was turned off, it was actually enabled in some cases. Fixing the issue in the build system as well as switching the check to verify that value of `SWIFT_RUNTIME_CLOBBER_FREED_OBJECTS` is taken into account in the sources. C/C++ implicitly defines macro values to 1 when set without a value and 0 when it is not set. Also making the hex a bit more recognizable and grep'able by including it as a comment. Fixes: rdar://149210738 (cherry picked from commit 6f39a52)
etcwilde
added
🍒 release cherry pick
|
@swift-ci please test |
tbkka
approved these changes
Apr 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
6.2 Cherry-Pick of: #81010
Disables clobbering free'd memory when
SwiftCore_ENABLE_CLOBBER_FREED_OBJECTSis set to off. The code inconsistently used#if SWIFT_RUNTIME_CLOBBER_FREED_OBJECTSand#ifdef SWIFT_RUNTIME_CLOBBER_FREED_OBJECTSto enable the clobbering. The flag setSWIFT_RUNTIME_CLOBBER_FREED_OBJECTSto0, which would partially enable it in the cases where#ifdefwas used. this makes the check consistent and fixes the build system to defineSWIFT_RUNTIME_CLOBBER_FREED_OBJECTSonly if it's enabled.Fixes: rdar://149210738
(cherry picked from commit 6f39a52)