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
400f0ab0b0
boot: fix flagsToBC
...
Why did I ever think that using CM was a good idea? any comparison
with numbers more than 0x8000 apart would be wrong...
2020-04-07 11:26:37 -04:00
Virgil Dupras
d013c572ad
Use proper RAM addr for HERE in SCPY
2020-04-04 07:34:38 -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
b162ef84f5
forth: fix broken RAM+
2020-04-02 13:42:49 -04:00
Virgil Dupras
941791d609
forth: remove RAMSTART and RS_ADDR from stable ABI
2020-04-02 11:39:40 -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
d0c5d3a741
Forth self-bootstraps!!!
...
This commit cuts Forth's dependency on zasm. It now self-assembles
its own boot-binary! Things are a bit messy now, I'll clean up
later.
2020-04-01 22:19:37 -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
25814c0b8b
forth: add label system to z80 assembler
2020-03-31 09:23:00 -04:00
Virgil Dupras
ce6e31dda1
forth: inline "strcmp"
2020-03-31 08:02:40 -04:00
Virgil Dupras
031bfc6d72
forth: setup SYSVNXT in Forth code
2020-03-30 21:48:56 -04:00
Virgil Dupras
e5ab0dd1c9
forth: a little bit of ASM routine inlining
2020-03-30 21:33:37 -04:00
Virgil Dupras
5c03b33982
forth: remove sysvarWord type
...
Not needed anymore. CONSTANT does the trick.
2020-03-30 21:19:48 -04:00
Virgil Dupras
05045b2aa4
forth: move stable ABI stuff at the top of forth.asm
...
Now we're having a real nice and tidy forth.asm...
2020-03-30 21:02:19 -04:00
Virgil Dupras
f366732424
forth: Forth-ify "DOES>"
2020-03-30 20:01:59 -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
da9f9f9899
forth: melt boot binary
2020-03-30 08:11:16 -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
7c9d799d93
forth: Forth-ify "SCMP"
2020-03-30 07:48:07 -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
