Repository navigation
0.5.1: the protocol marker survives a link that keeps only what it reaches - #8
Merged
Merged
Conversation
…aches Co-authored-by: speak-agent <[email protected]>
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 library, the GoogleTest adapter and the C ABI kept the marker (P2.3) by reading one byte of it, which the compiler folds to a constant; a link with
--gc-sectionsover per-object sections (mcpp test2026.11.9.1) then discarded it and the runner saw no protocol. They read its address through a volatile pointer. The conformance fixture is linked that way on Linux, so P2.3 checks it.Local:
mcpp testpasses for every member, with the released mcpp and with 2026.11.9.1's gc-linking test programs.Co-authored-by: speak-agent [email protected]