21
edits
Changes
m
REL files are loaded with OSLink. I have no idea if the information remains correct for REL files. RSO files are handled by RsoInit/RsoLoad.
Line 538:
Line 538:
== Dynamic linking ==
== Dynamic linking ==
−[[RSO]] files seem to be loaded through <code>OSLink</code>. At each relocation address, the instruction is patched with information about the base address depending on the relocation type. Types 1, 3, and 4 are identical and are used for 32-bit data, while type 2 is used for absolute branching instructions, type 5 is used for 16-bit data, type 6 is used for swapped endian, types 7-9 are used for absolute conditional branches, type 10 is used for relative branches, and types 11-13 are used for relative conditional branches. There is also a type 109 (0x6d - 'm') that has an unknown purpose.
+[[REL]] files are loaded through <code>OSLink</code>. At each relocation address, the instruction is patched with information about the base address depending on the relocation type. Types 1, 3, and 4 are identical and are used for 32-bit data, while type 2 is used for absolute branching instructions, type 5 is used for 16-bit data, type 6 is used for swapped endian, types 7-9 are used for absolute conditional branches, type 10 is used for relative branches, and types 11-13 are used for relative conditional branches. There is also a type 109 (0x6d - 'm') that has an unknown purpose.
<code>__OSModuleInit</code> writes NULL pointers to the module linked list head and tail, but no code in main binaries seems to write real pointers here; this is presumably done by the modules themselves.
<code>__OSModuleInit</code> writes NULL pointers to the module linked list head and tail, but no code in main binaries seems to write real pointers here; this is presumably done by the modules themselves.
[[Category:SDK]]
[[Category:SDK]]