A pad byte whose pair is not unique is located after the zoned zeros #670
Loading…
Reference in a new issue
No description provided.
Delete branch "rpg-9-ba-pad-pair-structure-20261029"
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?
A pad byte whose pair is not unique is located after the zoned zeros
The comparison normalizes the pad byte of the static initialization (a byte
of uninitialized compiler memory:
li rN,0xXX00; sth rN,D(r30)in the codeand
XX 00in the literals) only when itsXX 00pair is the only one inthe literals. When the byte is also the sign of a packed literal before a zero
byte (r6e-end:
2f 00three times), the rule located nothing and a recompilewith another pad byte differed in instructions and literals: about half of the
compiles of r6e-end, r6e-space, r6e-two-rec and r6e-ind-rec (ROUND9 4.2c,
4.2h).
In every r6e compile the pad pair follows a run of six zoned zeros
(
f0 f0 f0 f0 f0 f0 XX 00).compare_ile.zonedPadtakes that occurrence whenit is the only one;
findPadsuses it when the pair is not unique. The newprobe RECOMPILE/r6e-end is a recompile of r6e-end with another pad byte: it
matches the original (it differed in instructions and literals before).
Gates