Sync source edition with VCC Plus 3.7.0 build 63

This commit is contained in:
Brian Holman committed 2026-11-14 01:43:46 -07:00
1 parent c652a5276d
commit b2ecec4d87
86 files changed
+10519 -472

No files matched your search

+17 -2
View File
@@ -58,6 +58,16 @@ just the value written to an MMU register. Installed RAM capacity is checked by
the emulator. The packed binary's transfer address is `entryPoint`; it can belong
to a loader outside the unpacked C modules.
Verification uses distinct evidence budgets: the manifest is at most 1 MiB;
retained compiler `.s` assembly is at most 32 MiB per file; other evidence files
(including listings, objects, linker maps, executable and raw images) are at most
8 MiB each. Unique retained evidence is capped at 128 MiB in total. Files are
verified in full against their hashes; oversized evidence is rejected rather
than truncated. Rejections identify the artifact path, observed size and byte
limit. Existing limits on manifest records, module/page ownership and listing
rows still apply. Large generated type records in assembly do not relax the
assembler-listing row limits or establish a source mapping by themselves.
Declare each linker section under one module. `codeSections` names executable,
immutable sections; mutable data and BSS belong in `sections` with their real page
assignments but are excluded from code guards. BSS needs no invented raw zeros.
@@ -65,8 +75,13 @@ A pure BSS module may omit `image` entirely when `codeSections` is empty;
its explicit page assignments and section ownership still apply. An initialized
section cannot use that omission to skip object byte verification.
Keep mutable bytes out of executable sections. Split modules when unrelated pages
need not remain mapped together. Different overlays may reuse a logical address
only with distinct physical ownership.
need not remain mapped together. Version 1 permits logical-address reuse with
distinct physical ownership. For code images that replace one another in the
same physical RAM, use the explicit version-2
overlay group and owner contract. Runtime inspection
requires complete loaded-code proof of exactly one owner; declaration alone
does not establish residency. Build catalogs list static candidates, while a
paused inspection reports current verified ownership and a residency fingerprint.
Hashes bind the declaration to one build. VCC Plus independently replays object
relocations against the raw module bytes and verifies live RAM before publishing
+15 -3
View File
@@ -37,7 +37,11 @@ its `VCCDBG1` type/storage records; retaining compiler-generated `.s` permits
verification of records too long for an assembler listing row. A useful Debug
compile uses `-O0 -fno-omit-frame-pointer`; optimized builds can legitimately
have fewer C statements or unavailable locals. No user Makefile is rewritten
merely to provide debugger metadata.
merely to provide debugger metadata. Banked evidence permits compiler `.s` files
up to 32 MiB while retaining 8 MiB limits for other evidence, the 1 MiB manifest
limit and the 128 MiB aggregate cap. Size failures name the artifact and exact
limit; hash, declared-output and symbolic-link checks still apply. No evidence
is truncated to make a source map appear verified.
For example, a normal recipe can compile and link with:
@@ -51,7 +55,11 @@ program.bin: obj/main.o
This fragment only illustrates retained evidence; disk construction and launch
commands remain the project's declared recipe. Packed, relocated or bank-switched
programs must supply the public version-1 [banked debug manifest](MCP_BANKED_PLAYTEST.md).
programs must supply the public [banked debug manifest](MCP_BANKED_PLAYTEST.md).
Version 1 preserves distinct physical ownership; version 2 supports explicitly
declared mutually exclusive code overlays. Discover
`banked_debug_manifest_versions` and `verified_code_overlays` through
`get_capabilities` before preparing that evidence.
Its hashes, unpacked images, section ownership and actual physical page identities
are required. It never falls back to a flat interpretation after verification
fails.
@@ -82,7 +90,11 @@ Locally configured watches retain their existing rules.
`read_debug_memory` accepts only ranges advertised by that immutable snapshot,
up to 256 bytes. Resume, input, step, restart, source/artifact changes and
connection revocation invalidate the applicable observation. Inspection performs
connection revocation invalidate the applicable observation. Owned memory and
call-context reads also compare a fresh complete capture, including verified
residency, registers, cycles and safe memory, even at the same field clock.
The residency fingerprint names a current proof rather than a monotonic guest
write counter; A→B→A still requires fresh capture validation. Inspection performs
no guest expressions, register writes, memory writes or side-effecting I/O reads.
A mismatched binary, object relocation, source identity or bank cannot produce a
verified snapshot merely because a requested function name exists.