You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
32-bit relocation may become relevant in extended 65xx variant CPUs. This may be far-fetched, but even if not needed now, it should be defined at least as "reserved", so that no further changes will block this.
In the relocation table the type entry currently defines these types:
WORD $80 2 byte address
HIGH $40 high byte of an address
LOW $20 low byte of an address
SEGADR $c0 3 byte address (65816)
SEG $a0 segment byte of 3 byte address
To support 32-bit relocation, we assume that we do not need to handle the 3rd and 4th byte separately, and allow only high word relocation, in addition to 32 bit relocation:
LONG $e0 4 byte address
HWORD $60 upper 2 bytes of a 4 byte address
In the case of HWORD, the entry is followed by the lower two bytes of the address similar to the low byte of a HIGH relocation.
The text was updated successfully, but these errors were encountered:
32-bit relocation may become relevant in extended 65xx variant CPUs. This may be far-fetched, but even if not needed now, it should be defined at least as "reserved", so that no further changes will block this.
In the relocation table the type entry currently defines these types:
To support 32-bit relocation, we assume that we do not need to handle the 3rd and 4th byte separately, and allow only high word relocation, in addition to 32 bit relocation:
In the case of HWORD, the entry is followed by the lower two bytes of the address similar to the low byte of a HIGH relocation.
The text was updated successfully, but these errors were encountered: