Sync source edition with VCC Plus 3.7.0 build 63
This commit is contained in:
1 parent
c652a5276d
commit
b2ecec4d87
86 files changed
+10519
-472
No files matched your search
@@ -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
|
||||
|
||||
Reference in new issue
Block a user