collapseos/blk/393

: RAM+ [ RAMSTART LITN ] + ;
: BIN+ [ BIN( @ LITN ] + ;
: HERE 0x04 RAM+ ;
: CURRENT* 0x51 RAM+ ;
: CURRENT CURRENT* @ ;

( w -- a f )
: (find) CURRENT @ SWAP _find ;

: QUIT
    (resRS)
    0 0x08 RAM+ !  ( 08 == C<* override )
    LIT< INTERPRET (find) DROP EXECUTE
;
1 20 LOADR+
Move icore to blkfs The way is clear for complete stage1 bootstrapping on the RC2014 target! 2020-04-24 05:14:14 +10:00			`: RAM+ [ RAMSTART LITN ] + ;`
icore: add BIN+ This allows us to write LATEST at proper offset in emul/stage1.fs in cases where we set a nonzero BIN(. 2020-04-30 01:42:09 +10:00			`: BIN+ [ BIN( @ LITN ] + ;`
Move icore to blkfs The way is clear for complete stage1 bootstrapping on the RC2014 target! 2020-04-24 05:14:14 +10:00			`: HERE 0x04 RAM+ ;`
			`: CURRENT* 0x51 RAM+ ;`
			`: CURRENT CURRENT* @ ;`

			`( w -- a f )`
			`: (find) CURRENT @ SWAP _find ;`

Stop LOADing on ABORT This is done by adding a "C<* override" layer that is reset to 0 on ABORT. The problem was that when ABORT happened during a LOAD, we had a resetted RSP and started from a clean INTERPRET, but LOAD didn't have the opportunity to restore C<, which caused it to continue interpreting from the faulty BLK. With a C< override, we don't need to restore C<*, we just need to clear the override. 2020-04-25 04:10:40 +10:00			`: QUIT`
			`(resRS)`
			`0 0x08 RAM+ ! ( 08 == C<* override )`
			`LIT< INTERPRET (find) DROP EXECUTE`
			`;`
blk: Add LOAD+ and LOADR+ And use them in all places they make sense. 2020-05-05 11:43:48 +10:00			`1 20 LOADR+`