diff options
| author | Andreas Baumann <mail@andreasbaumann.cc> | 2020-01-25 21:32:03 +0100 |
|---|---|---|
| committer | Andreas Baumann <mail@andreasbaumann.cc> | 2020-01-25 21:32:03 +0100 |
| commit | 1387c084773c481c62924b3f98f93c60f790156b (patch) | |
| tree | 154645592f83f87a9a69ce5b186a158a9737c480 /crenshaw | |
| parent | 29d0fec3cf812bb691a1adb98ea19f0cf7b162e8 (diff) | |
| download | compilertests-1387c084773c481c62924b3f98f93c60f790156b.tar.gz compilertests-1387c084773c481c62924b3f98f93c60f790156b.tar.bz2 | |
first implementation of memory management
Diffstat (limited to 'crenshaw')
| -rw-r--r-- | crenshaw/README | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/crenshaw/README b/crenshaw/README index 244c0be..9797e1b 100644 --- a/crenshaw/README +++ b/crenshaw/README @@ -22,7 +22,7 @@ fpc main.pas nasm -o test.bin -f bin test.asm ./emul test.bin -TODO: kapstone to actually assemble the code, currently +TODO: capstone to actually assemble the code, currently we use nasm to produce a binary and we use capstone to decode it. What's better? @@ -87,7 +87,7 @@ but we still have to calculate relative addresses. On the other hand we loose a register as sort of an address base register. -PC-relative adressig is a good thing, as it makes +PC-relative adressing is a good thing, as it makes code relocatable for free. Some survey on which CPUs have/had PC-relative adressing: |