openkal-linux 0.16.1 and openkal-musl 0.20.1 - #509
Merged
Merged
Conversation
The repair release, and the C library port that reaches it. Both GLOBAL addresses are the upstream tag archives and both CN addresses are the byte-identical gitcode assets, checked against the recorded sha256 for each. openkal-linux 0.16.1 places the program's thread-local image where the linker measured it; openkal-musl 0.20.1 moves its pin, which is what makes the repair reach a consumer of the C library.
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.
The repair release and the C library port that reaches it.
openkal-linux0.16.1 places the program's thread-local image where the linker measured it — a latent defect its own 0.16.0 made visible, reported byopenkal-llvm-runtime's probe on the runner.openkal-musl0.20.1 is a pin move: a consumer of the C library names one implementation, and this is the release that names the repaired one.Every sha256 was taken from the upstream tag archive and confirmed against the byte-identical gitcode asset, for each of the three platform tables.