docs: #693-#696 records landed, with the release and ecosystem readings - #700
Merged
Merged
Conversation
The plan's status moves to landed, and its implementation record (§12.4 to §12.6, Appendix A.15) states what was released and measured: - mcpp 2026.9.26.1 (#698), xlings 2026.9.26.2 (openxlings/xlings#613), openkal-musl 0.19.2 and openkal-llvm-runtime 0.15.2, each mirrored to GitCode and checked against its GitHub sha256, and registered or indexed; - the sandbox check of the published artefacts (12 ok) and the same script against 2026.9.25.1 (exactly the six criteria the release changes fail); - mcpp-index#469's sweep (green on every platform) and its openkal measurement over four targets, where the one cell #696 makes visible, mimalloc's `-latomic` on the linux-musl rows, is filed with its owner (mcpplibs/openkal-llvm-runtime#31); - the self-review, and what remains open with the reason for each.
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
2 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.
The plan's status moves to landed, and its implementation record (§12.4 to
§12.6, Appendix A.15) states what was released and measured:
openkal-musl 0.19.2 and openkal-llvm-runtime 0.15.2, each mirrored to GitCode
and checked against its GitHub sha256, and registered or indexed;
against 2026.9.25.1 (exactly the six criteria the release changes fail);
measurement over four targets, where the one cell Links over a graph-supplied C library still search the host's /usr/lib: -lm breaks aarch64-linux-musl and can link glibc code into x86_64-linux-musl #696 makes visible,
mimalloc's
-latomicon the linux-musl rows, is filed with its owner(-latomic has no answer in the openkal graph on linux-musl targets mcpplibs/openkal-llvm-runtime#31);