0.20.1 --- openkal-linux 0.16.1 beneath - #51
Merged
Merged
Conversation
The pin moves and nothing else does. 0.16.1 repairs where openkal-linux copies the program's thread-local image (found by openkal-llvm-runtime's own probe against 0.16.0), and this port is what reaches that implementation: a version written without an operator is an exact pin in mcpp, so a consumer naming this C library and the implementation it runs on names one of each and not two. Nothing in this package changes with it. The region a context stands on was measured before the repair and is measured the same way after it, and `examples/stack-bounds` reports the same three readings.
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
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 pin moves and nothing else does.
openkal-linux0.16.1 repairs where that implementation copies the program's thread-local image — a latent defect its own 0.16.0 made visible, reported byopenkal-llvm-runtime's probe. A version written without an operator is an exact pin in mcpp, so a consumer naming this C library and the implementation it runs on names one of each and not two.Nothing in this package changes with it: the region a context stands on is measured the same way, and
examples/stack-boundsreports the same three readings (first e=0 contains=1,started contains=1,another thread refused=1).