generated from erix/meta
[BUG] Main boot consumers still use V1 after handoff moved to V2 #25
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/bootloader#25
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Bootloader and Kernel main still consume the V1 boot handoff, but lib-handoff main now exports V2. A build using their declared main dependencies cannot compile these consumers.
Reproduction
Use Bootloader
1d234d9148c5183c552a3c0964d9a1bbbdbd9ff6, Kernel9b120c8703c85001bfaacbcaa6e996b8d4fd98c6and lib-handoffa96a35ddb9208cd6a2d66b1351c9282f817797d3.Build the Bootloader tests with actual main providers. Its handoff builder imports
BL_KERNEL_HEADER_V1_SIZE,BL_KERNEL_MAGIC_V1andBlKernelHandoffHeaderV1; the selected provider exports the V2 replacements. Kernel ingress and its entry boundary have the same V1 dependency.Expected and actual behavior
Current consumers should serialize and validate the V2 contract, retaining complete counted names and their original store bounds. The observed compiler run fails with nine errors for missing V1 items and resulting type inference failures.
Environment and identity
41930448e25d4e188895871db66f73610ada4a83.Evidence and prior checks
Bootloader run 289 compiles a handoff builder byte-identical to Bootloader main against the V2 provider and records the missing items. Main's green CI selects an older companion, so it does not prove compatibility with the declared main provider.
Tracking
Related implementations: Bootloader #24 and Kernel #127. Current-main replacements must be qualified together before an actual boot or release claim.