collapseos/blk/298

CODE (loop)
PC ORG @ 0x45 + ! ( stable ABI JP )
    0 IX+ INC(IXY+), IFZ, 1 IX+ INC(IXY+), THEN, ( I++ )
    ( Jump if I <> I' )
    A 0 IX+ LDrIXY, 2 IX- CP(IXY+), JRNZ, L1 BWR ( branch )
    A 1 IX+ LDrIXY, 1 IX- CP(IXY+), JRNZ, L1 BWR ( branch )
    ( don't branch )
    IX DECd, IX DECd, IX DECd, IX DECd,
    IY INCd,
;CODE
z80: move boot code around Bring native words together, make the next/exec/does/compiled cluster be at the beginning. Next step: bring find code into _find word. 2020-07-05 22:23:40 -04:00			`CODE (loop)`
			`PC ORG @ 0x45 + ! ( stable ABI JP )`
			`0 IX+ INC(IXY+), IFZ, 1 IX+ INC(IXY+), THEN, ( I++ )`
			`( Jump if I <> I' )`
			`A 0 IX+ LDrIXY, 2 IX- CP(IXY+), JRNZ, L1 BWR ( branch )`
			`A 1 IX+ LDrIXY, 1 IX- CP(IXY+), JRNZ, L1 BWR ( branch )`
			`( don't branch )`
			`IX DECd, IX DECd, IX DECd, IX DECd,`
Make br cells 1 byte wide The 1 byte limitation has been effective for a while now, but I hadn't made the move yet, I wanted to see if the limitation would cause me problems. It doesn't. Doing this now slightly facilitates the IY->BC move in z80. Bootstrapping: if you try to recreate the CVM binary from the previous commit with this code, you'll have bootstrapping problems. The first bootstrap will compile a binary with 2-bytes wide cells but branching conditionals that yields 1-byte cells. That's bad. I got around the issue by temporarily inserting a "397 399 LOADR" instruction in cvm/xcomp.fs, right before the xcomp overrides. This way, I force 1-byte cells everywhere on the first compiliation, which then allows me to apply the logic change in cvm/vm.c and have a properly running binary. 2020-07-06 07:27:50 -04:00			`IY INCd,`
z80: move boot code around Bring native words together, make the next/exec/does/compiled cluster be at the beginning. Next step: bring find code into _find word. 2020-07-05 22:23:40 -04:00			`;CODE`