Skip to content

Name the conformance section that exists, not one that does not #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Sunrisepeak merged 1 commit into from
Aug 27, 2026
Merged

Name the conformance section that exists, not one that does not #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 16 additions & 6 deletions src/exec.cpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,14 +20,24 @@
// SAME TIME --- `MAP_JIT' and the pair of calls that flip one region between
// the two. It is not what a program needs to obtain memory that is writable,
// then made executable and no longer writable, which is the whole of what this
// interface offers. tests/conformance_exec.cpp is where that distinction stops
// being an argument: it reserves a region, writes an instruction sequence into
// it, publishes it, CALLS it, and compares what it returned.
// interface offers.
//
// ⇒ If that test fails on this system, the reading above is wrong and the
// ⭐ THE SPECIFICATION'S OWN SUITE IS WHERE THAT DISTINCTION STOPS BEING AN
// ARGUMENT --- `conformance/src/sections/exec.cpp' in the openkal repository,
// which this package runs through `run-conformance.sh openkal-macos .
// full,optional'. It reserves a region, writes an instruction sequence into it,
// publishes it, CALLS it, and compares what it returned.
//
// ⚠️ An earlier version of this comment named `tests/conformance_exec.cpp',
// which is in this repository and does not exist. A comment naming the place a
// question is answered is a promise, and one pointing at nothing sends a reader
// to look and leaves them unable to tell whether the check is missing or the
// reference is.
//
// ⇒ If that section fails on this system, the reading above is wrong and the
// remedy is clause 6.5's: a feature of this package, provided at dependency
// resolution, together with whatever produces the artifact. The test is here so
// that the question is answered by the system rather than by this comment.
// resolution, together with whatever produces the artifact. The question is
// answered by the system rather than by this comment.
//
// ⚠️⚠️ THE INSTRUCTION CACHE IS NOT INVALIDATED HERE, AND ONE VERSION OF THIS
// FILE DID INVALIDATE IT. THE MEASUREMENT IS WHY IT DOES NOT.
Expand Down
Loading