1
0
mirror of https://github.com/catseye/SixtyPical.git synced 2024-11-29 18:49:22 +00:00

We really need to review how storage location labels are emitted.

This commit is contained in:
Chris Pressey 2017-12-08 16:59:31 +00:00
parent 84ca6c4e96
commit 404f8c72a3
2 changed files with 54 additions and 0 deletions

View File

@ -42,6 +42,17 @@ class Word(Emittable):
return "%s(%r)" % (self.__class__.__name__, self.value)
class Table(Emittable):
def size(self):
return 256
def serialize(self, addr=None):
return chr(0) * self.size()
def __repr__(self):
return "%s()" % (self.__class__.__name__)
class Label(Emittable):
def __init__(self, name, addr=None):
self.name = name

View File

@ -239,6 +239,49 @@ Indexed access.
| }
= 00c0a200a9009d0dc0bd0dc060
Byte tables take up 256 bytes in memory. This is clearer if you disassemble the output,
but what we don't want to see, is something like:
$800E LDX #$00
$8010 LDA $0816,X
$8013 STA $0818,X
$8016 RTS
| byte table tab1
| byte table tab2
|
| routine main
| inputs tab1
| outputs tab2
| trashes a, x, n, z
| {
| ld x, 0
| ld a, tab1 + x
| st a, tab2 + x
| }
= 00c0a200bd09c09d0bc060
Byte storage locations take up only 1 byte in memory. This is clearer if you disassemble the output,
but what we don't want to see, is something like:
$800E LDX #$00
$8010 LDA $0816
$8013 STA $0818
$8016 RTS
| byte one
| byte two
|
| routine main
| outputs one, two
| trashes a, x, n, z
| {
| ld a, 0
| st a, one
| st a, two
| }
= 00c0a200bd09c09d0bc060
Copy byte to byte.
| byte bar