Compiler.ELF

Larger LOAD segment (4 MiB) for the PHYSICAL native-program path only (nvctl/GPU probes whose interpreted image body + embedded kernel + upload payloads exceed the 256 KiB fixedZeroELFHeader segment). The header LENGTH is byte-identical to fixedZeroELFHeader (120 bytes), so the machine code still starts at file offset 120 and the interpreter's state/scratch base is unchanged; only the mapped segment END moves out from 0x440000 to 0x800000. The self-host compiler ELF path (compileClosedZeroExecutable -> wrapMachineCode) is deliberately NOT changed, so its byte-identity is preserved. p_filesz = p_memsz = 0x00400000 (4 MiB); the file is padded to cover it. The old 1-MiB physical segment was smaller than a valid 4,242-command checkpoint-resume program: Linux mapped only 0x400000..0x500000 and execution faulted exactly at the unmapped 0x500000 boundary.

122def zeroPadding524288 : Bytes =
123  (bytes-append zeroPadding262144 zeroPadding262144)