Repository navigation
ci: mcpp 2026.11.12.1; the longjmp probe runs - #19
Merged
Merged
Conversation
…s first compiled by the engine that resolves its key)
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.
mcpp 2026.11.12.1 is released and in the index; it knows
[target.<selector>.abi] longjmp.MCPP_VERSION: 2026.11.12.1in CI.longjmpprobe (0.14.1 kept it behind a step that skipped while the engine refused the key) runs without the skip branch: the manifest stateslongjmp = "wasm", the engine renders-sSUPPORT_LONGJMP=wasmon the C and C++ units and on the link, and the probe's round trip is the criterion.No change to the library or its version.
What the first real run of the probe found
The probe had never been compiled: every engine before 2026.11.12.1 refused its manifest's key, and the step skipped. Its first build failed twice, on the probe and not on the engine or the library:
unknown type name 'sigjmp_buf': the C library declaressigsetjmpandsiglongjmponly to a unit that asks for POSIX, and the engine compiles C at the standard alone. The unit states_POSIX_C_SOURCE 200809L.no binary target in this package: the engine infers a program fromsrc/main.cpp; the probe is C and states its target.With both,
mcpp run --target wasm32-emscriptenexits 0 under the payload's node with mcpp 2026.11.12.1 (measured locally with the release installed through xlings;-sSUPPORT_LONGJMP=wasmis on the compile and link lines).