Virgil Dupras
1b6286dcfe
Make (find) 2-layered, the lower layer having CURRENT as a param
2020-04-09 11:20:54 -04:00
Virgil Dupras
0c3067ed9a
icore: simplify definition of ":" and ";"
2020-04-09 09:38:59 -04:00
Virgil Dupras
784b109652
So, why was ":" an immediate again?
2020-04-09 09:27:51 -04:00
Virgil Dupras
afed423530
Remove memory maps
...
It was a dead end. my new tentative solution is xcomp.
2020-04-09 09:21:55 -04:00
Virgil Dupras
68f359d6c2
Add xcomp unit for cross compilation
...
Memory mapping is a dead end too, solution has to be at a higher
level. xcomp is my new approach.
2020-04-09 08:23:53 -04:00
Virgil Dupras
2a2e3a64a4
Move IMMED? from z80c to icore
2020-04-08 20:09:32 -04:00
Virgil Dupras
a7a2f3d08b
Move IMMEDIATE from z80c to core
...
This makes IMMEDIATE affected by memory mappings.
2020-04-08 19:43:44 -04:00
Virgil Dupras
64e441d059
Move SCPY from z80c to icore
...
This way, it can be affected by memory mappers.
2020-04-08 16:12:34 -04:00
Virgil Dupras
ba918d0fef
Add memory maps
2020-04-07 20:54:10 -04:00
Virgil Dupras
521ff84ca4
Reserve some RAM for future features
2020-04-07 17:32:04 -04:00
Virgil Dupras
2af959a13d
Don't use IMMEDIATE in icore
...
Since the fix of its RAM addr, we use the wrong CURRENT in every
usage of IMMEDIATE in icore. We therefore have to manually set the
flag for all 3 immediate words in that unit.
2020-04-04 08:40:55 -04:00
Virgil Dupras
80891d7ec1
Add in-memory bootstrapping system
...
This should help with the bootstrapping of non-emulated environment.
For example, I have a problem with the RC2014: I can't send it
bootstrap info until the ACIA is up. I need to find a way...
2020-04-03 20:13:11 -04:00
Virgil Dupras
b575d7f863
Move (print) and (uflw) from icore to core
2020-04-03 07:44:44 -04:00
Virgil Dupras
c56386af02
wip
2020-04-02 23:21:53 -04:00
Virgil Dupras
b162ef84f5
forth: fix broken RAM+
2020-04-02 13:42:49 -04:00
Virgil Dupras
2481ed4b66
forth: remove dummy.fs
...
All "stop pings" are now explicitly made at appropriate places. This
fixes a problem I've introduced in the last commit where RAM+ was
unexpectedly part of a stable ABI because of "HERE" usage in dummy.fs.
This system will, anyways, soon change because boot.bin and z80c.bin
will be built during the same process (but there's a bit of retooling
to do before I get there).
2020-04-02 11:29:23 -04:00
Virgil Dupras
68a7be3707
forth: Remove RAM offsets from stable ABI
...
Doing this was a bit stupid. These offsets are constants. Moreover,
having them in stable ABI had us construct the boot binary from the
stable ABI of the host, making it very difficult to change RAMSTART
for a new system.
2020-04-02 10:20:51 -04:00
Virgil Dupras
b7244f8985
forth: shrink forth.asm's binary size
2020-03-31 22:11:44 -04:00
Virgil Dupras
1e85d60d89
forth: Forth-ify ","
2020-03-31 16:32:50 -04:00
Virgil Dupras
7d5b1f5cea
forth: Forth-ify parseDecimal
2020-03-31 15:04:28 -04:00
Virgil Dupras
36e200adbb
forth: Forth-ify "SCPY"
2020-03-30 17:59:30 -04:00
Virgil Dupras
5b01f797fc
forth: Forth-ify "(find)"
2020-03-30 17:36:15 -04:00
Virgil Dupras
de3da19333
forth: Forth-ify "NOT"
2020-03-30 17:26:51 -04:00
Virgil Dupras
4756fb7763
forth: Forth-ify "(parsed)"
2020-03-30 17:21:13 -04:00
Virgil Dupras
80985460d4
forth: remove JTBL
...
We refer to stable offset as direct numbers instead of offset to JTBL.
Simpler that way.
2020-03-30 17:05:00 -04:00
Virgil Dupras
61195a987d
forth: Forth-ify "HERE", "CURRENT" and "JTBL"
2020-03-30 15:11:23 -04:00
Virgil Dupras
a9cf861cfd
forth: Forth-ify "(parse*)"
2020-03-30 14:49:20 -04:00
Virgil Dupras
f9d45f7f53
forth: Forth-ify "FLAGS"
2020-03-30 14:29:21 -04:00
Virgil Dupras
162ff2c5cb
forth: Forth-ify "!"
2020-03-30 14:09:39 -04:00
Virgil Dupras
8ef9e7d0da
forth: Forth-ify "@"
2020-03-30 14:05:07 -04:00
Virgil Dupras
f9c3a0444c
forth: Forth-ify "DROP"
2020-03-30 13:57:06 -04:00
Virgil Dupras
49994f09ce
forth: add word "2DROP"
2020-03-30 13:54:46 -04:00
Virgil Dupras
8186511727
forth: fix bootstrapping issues with "LITN" and "+"
2020-03-30 13:50:53 -04:00
Virgil Dupras
395eb04fac
forth: Forth-ify "C<"
2020-03-30 08:37:33 -04:00
Virgil Dupras
f6cba4b1cf
forth: Forth-ify "QUIT"
2020-03-30 08:25:22 -04:00
Virgil Dupras
d09ec0d757
forth: Forth-ify "SWAP"
2020-03-30 08:06:11 -04:00
Virgil Dupras
cc4700e389
forth: Forth-ify "DUP"
2020-03-30 08:02:20 -04:00
Virgil Dupras
09cd25df29
forth: Forth-ify "OVER"
2020-03-30 07:58:16 -04:00
Virgil Dupras
9cfddea940
forth: Forth-ify "+"
2020-03-30 07:54:45 -04:00
Virgil Dupras
a2c258afba
forth: Forth-ify "CMP"
...
forth.asm under 1K lines!
2020-03-30 07:52:24 -04:00
Virgil Dupras
48078d9c9c
forth: Replace "SKIP?" with "(?br)"
...
There is an alternate git history where I continued the Forth-ification of
words, including "SKIP?", but that was a bad idea: because that word was
written by flow control immediates, I stepped into quicksands where stability
became necessary in z80c.fs and I couldn't gracefully get out of it.
I'm stepping back and take this opportunity to replace the shoddy SKIP? algo
with a more straightforward (?br) implementation.
(br) and (?br) will always stay in boot code where it's easier manage a stable
ABI.
2020-03-29 09:10:23 -04:00
Virgil Dupras
9fcfebd84c
forth: Forth-ify "WS?"
2020-03-28 13:18:43 -04:00
Virgil Dupras
c1693c6256
forth: Forth-ify "TOWORD"
2020-03-28 13:02:04 -04:00
Virgil Dupras
8b7947bc6a
forth: Forth-ify "WORD"
2020-03-28 12:55:22 -04:00
Virgil Dupras
758ec025dc
forth: Forth-ify "LITN"
2020-03-28 10:38:05 -04:00
Virgil Dupras
1227ee7155
forth: Forth-ify "EMIT"
2020-03-28 10:25:02 -04:00
Virgil Dupras
e0eaa8ba63
forth: Forth-ify "ABORT"
2020-03-28 10:11:52 -04:00
Virgil Dupras
ab98e9bcd1
forth: Forth-ify "(uflw)"
2020-03-28 09:19:40 -04:00
Virgil Dupras
5471ef02a7
forth: Forth-ify "BOOT"
2020-03-28 09:08:46 -04:00
Virgil Dupras
408d93bd23
forth: Forth-ify "IMMED?"
2020-03-27 21:58:24 -04:00
