offsets for label definitions, immediates
This commit is contained in:
parent
53c8c9939d
commit
e3ccf5d976
3 changed files with 20194 additions and 33 deletions
|
@ -319,19 +319,18 @@ very end:
|
||||||
00 00 00 00 00 00 00 00
|
00 00 00 00 00 00 00 00
|
||||||
00 00 40 00 00 00 00 00
|
00 00 40 00 00 00 00 00
|
||||||
00 00 00 00 00 00 00 00
|
00 00 00 00 00 00 00 00
|
||||||
00 00 03 00 00 00 00 00
|
00 00 08 00 00 00 00 00
|
||||||
00 00 03 00 00 00 00 00
|
00 00 08 00 00 00 00 00
|
||||||
00 10 00 00 00 00 00 00
|
00 10 00 00 00 00 00 00
|
||||||
</code></pre>
|
</code></pre>
|
||||||
|
|
||||||
This is at the position for `||`, and it contains the ELF header. One thing you
|
This is at the position for `||`, and it contains an ELF header. One thing you
|
||||||
might notice is that we decided that each entry is 8 bytes long, but this one is
|
might notice is that we decided that each entry is 8 bytes long, but this one is
|
||||||
0x79 = 121 bytes long! It's okay, our code doesn't actually check that we're
|
0x79 = 121 bytes long! It's okay, our code doesn't actually check that we're
|
||||||
using less than 8 bytes of data, but it means that the entries for certain
|
using less than 8 bytes of data, but it means that the entries for certain
|
||||||
commands, e.g. `}\n` will land right in the middle of the data for the ELF
|
commands, e.g. `}\n` will land right in the middle of the data for the ELF
|
||||||
header. But by a lucky coincidence, all those entries actually land on 0 bytes,
|
header. But by a lucky coincidence, all those entries actually land on 0 bytes,
|
||||||
so they'll just be treated as unrecognized (as they should be). So it's all
|
so they'll just be treated as unrecognized (as they should be).
|
||||||
good.
|
|
||||||
|
|
||||||
## limitations
|
## limitations
|
||||||
|
|
||||||
|
|
4
02/in02
4
02/in02
|
@ -1,3 +1,3 @@
|
||||||
::hw
|
::hw
|
||||||
jm
|
##37cab123abcdef12.
|
||||||
--hw
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue