Repository navigation
0.23.0 --- an image at its base; exec regions zero, sealed and mapped privately; attenuated grants and confinement; faults, fault reports, samples and touches; resource preference - #61
Merged
Conversation
Sunrisepeak
force-pushed
the
openkal-0.23
branch
from
November 2, 2026 18:33
97fab19 to
e9ddc0b
Compare
Sunrisepeak
changed the title
Sunrisepeak
force-pushed
the
openkal-0.23
branch
from
November 2, 2026 18:51
e9ddc0b to
4dad97b
Compare
…ROP_PLACE, the placement note, clause 12.4 version 1.1); a name with every link followed (kal_fs_resolved_name, KAL_FS_PROP_RESOLVED_NAME) Co-authored-by: speak-agent <248744407+speak-agent@users.noreply.github.com>
Sunrisepeak
force-pushed
the
openkal-0.23
branch
from
November 2, 2026 19:03
4dad97b to
f8fc391
Compare
…part sealed read-only (kal_exec_seal_part); a part read in, and executed with branch targets (KAL_EXEC_MAP_PREFETCH, _BTI); a handle with less (kal_fs_dir_attenuate: read-only, unchanging, recorded); a listing with attributes (kal_fs_list_next_info); confinement (KAL_SPAWN_CONFINE); page faults counted; a fault reported by what ends the program; samples; the resource preference (kal_env_resources) and what memory there is (kal_memory_info); the end of a listing stated Clause 11 entries 50 to 57, clauses 7.16 and 7.17, 12.3 and 12.4 (types 4 and 5). The conformance suite observes each; openkal.prof and openkal.debug are named in `optional', as an implementation now provides them to a program built for its environment. Co-authored-by: speak-agent <248744407+speak-agent@users.noreply.github.com>
…n by the environment (KAL_PROF_PROP_TOUCHES and three operations); clause 11 entry 56 Co-authored-by: speak-agent <248744407+speak-agent@users.noreply.github.com>
… the program writes them, never executed; clause 11 entry 52 Co-authored-by: speak-agent <248744407+speak-agent@users.noreply.github.com>
Sunrisepeak
changed the title
…the sandbox's reads, Windows' file parts, the touch note the producer's) Co-authored-by: speak-agent <248744407+speak-agent@users.noreply.github.com>
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.
openkal 0.23.0 (mcpp design 2026-11-02 part 3, 2026-11-03 part 4)
An image at its base.
kal_exec_alloc_atreserves an exec region at an address, or answers null with nothing reserved (KAL_EXEC_PROP_PLACE); the placement note (clause 12.4, type 3, clause version 1.1); a loader given the base applies only symbol relocations (12.3). Entry 48. Type 4 (touch) and type 5 (a loader's own prepared copy, never distributed) are defined.Names and listing.
kal_fs_resolved_name(every link followed,KAL_FS_PROP_RESOLVED_NAME);kal_fs_list_next_info(a listing with each entry's size, times and identity,KAL_FS_PROP_LIST_INFO, entry 54); the end of a listing stated (kal_ok, iterator zero, name empty).Exec regions. A region is zero when returned (entry 50);
kal_exec_seal_partmakes a part read-only, for good withKAL_EXEC_SEAL_FOREVER(entry 51);KAL_EXEC_MAP_PREFETCH,KAL_EXEC_MAP_BTIandKAL_EXEC_MAP_WRITE(a private copy-on-write part, never executed; entry 52).Capabilities.
kal_fs_dir_attenuatewithKAL_DIR_READ_ONLY,KAL_DIR_UNCHANGINGandKAL_DIR_RECORDED(the record format, rights passed with a grant);KAL_SPAWN_CONFINE(KAL_PROCESS_PROP_CONFINE, opt-in) (entry 53).Observation.
KAL_PINFO_FAULTS/MAJOR(entry 55);openkal.debug's fault report (KAL_DEBUG_PROP_FAULT_REPORT) andopenkal.prof's samples (kal_prof_sample_*,KAL_PROF_PROP_SAMPLES) and touches (kal_prof_touch_*,KAL_PROF_PROP_TOUCHES), taken by the environment (entry 56).Resources.
kal_env_resourcesandKAL_SPAWN_RESOURCES_{BALANCED,PERFORMANCE,ECONOMY};kal_memory_info(entry 57).Conformance observes every addition (
region,prof,debugfeatures); declarations, macros and the surface are regenerated. Every implementation passes it on CI: openkal-linux 0.24.0, openkal-macos 0.21.0, openkal-windows 0.19.0, openkal-emscripten 0.12.0.