izaya/collapseos
1
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
d8d2e05eb2
collapseos/blk/812

17 lines
731 B
Plaintext
Raw Normal View History

pcat: begin porting forth I'm not sure yet where I'm going, but I'm not going to build the 8086 port from the ground up like I did with the z80, that is, making is sustain itself and eventually merge its forth code with core words. That would be too much work which would then be thrown out (all those words I'll initially have to implement in asm which are already implemented in Forth). What I *think* I can do is build a mirror version of z80 boot code and cross-compile it from the z80. This means it has to follow z80 stable ABI. Nope, I'm not sure where I'm going...
2020-06-13 21:37:54 -04:00
( Registers. SP -> PSP DX -> RSP CX -> IP )
pcat: use a far jump to boot into the OS Unless I misunderstood, this is supposed to set CS. This would make all SREG have the same value. This allows us to remove BIN( offset from os.bin. I've tried booting to offset 0, but it didn't seem to work. Let's settle for 0x8000. 512kb of system RAM is way more than we need anyways.
2020-06-13 20:06:51 -04:00
H@ ORG !
pcat: begin porting forth I'm not sure yet where I'm going, but I'm not going to build the 8086 port from the ground up like I did with the z80, that is, making is sustain itself and eventually merge its forth code with core words. That would be too much work which would then be thrown out (all those words I'll initially have to implement in asm which are already implemented in Forth). What I *think* I can do is build a mirror version of z80 boot code and cross-compile it from the z80. This means it has to follow z80 stable ABI. Nope, I'm not sure where I'm going...
2020-06-13 21:37:54 -04:00
JMPn, 0 A,, ( 00, main ) JMPn, 0 A,, ( 03, find )
0 A,, ( 06, unused ) 0 A,, ( 08, LATEST )
0 A, ( 0a, unused ) JMPn, 0 A,, ( 0b, cellWord )
JMPn, 0 A,, ( 0e compiledWord ) JMPn, 0 A,, ( 11, pushRS )
JMPn, 0 A,, ( 14, popRS )
pcat: make find compare strings find is the biggest chunk of logic of the boot code. The 8086 version is significantly terser than the z80 one. REP/CMPS helps...
2020-06-15 06:23:19 -04:00
DI JMPr, ( 17, nativeWord ) 0 A,
pcat: begin structuring around words
2020-06-14 14:15:44 -04:00
JMPn, 0 A,, ( 1a, next ) JMPn, 0 A,, ( 1d, unused )
pcat: begin porting forth I'm not sure yet where I'm going, but I'm not going to build the 8086 port from the ground up like I did with the z80, that is, making is sustain itself and eventually merge its forth code with core words. That would be too much work which would then be thrown out (all those words I'll initially have to implement in asm which are already implemented in Forth). What I *think* I can do is build a mirror version of z80 boot code and cross-compile it from the z80. This means it has to follow z80 stable ABI. Nope, I'm not sure where I'm going...
2020-06-13 21:37:54 -04:00
0 A, 0 A, ( 20, numberWord ) 0 A, 0 A, ( 22, litWord )
0 A, 0 A, ( 24, addrWord ) 0 A, 0 A, ( 26, unused )
0 A, 0 A,, ( unused )
JMPn, 0 A,, ( 2b, doesWord ) 0 A, 0 A, ( 2e, unused )
0 A, 0 A,, ( unused )
JMPn, 0 A,, ( 33, execute ) 0 A, 0 A, ( unused )
0 A, 0 A,, ( unused )
Reference in New Issue Copy Permalink