Fix jl_set_precompile_field_replace for 0-size fields
#58155
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
topolarity
added
bugfix
vtjnash
approved these changes
Apr 17, 2025
KristofferC
pushed a commit
that referenced
this pull request
Apr 22, 2025
(cherry picked from commit 7341098)
51 tasks
KristofferC
removed
the
backport 1.12
LebedevRI
pushed a commit
to LebedevRI/julia
that referenced
this pull request
May 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
We need to make sure this doesn't end up in the
bits_replacetable, or else we can be confused by these non-unique field addresses.This makes
Base.OncePerProcess{Nothing}work during pre-compilation