A self-descriptive stack-based PC platform
git clone git://git.luxferre.top/equi.git
Log | Files | Refs | README | LICENSE

commit f5fe3b6a151be0fbf25f44b6afc0511689c96237
parent 887e637e28b5d7e312410cc62aa01464ff064ee8
Author: Luxferre <lux@ferre>
Date:   Sun, 14 Aug 2022 22:20:07 +0300

Attempt to somehow streamline the readme

MREADME.md | 2--
1 file changed, 0 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md @@ -59,8 +59,6 @@ varies |Compilation lookup table varies |General purpose data (GPD) area -To preserve runtime integrity, Equi implementations are allowed to (but not required to) restrict all writes to the addresses below the GPD area start. Note that command buffer area must not be write-restricted, i.e. Equi programs can be self-modifying. Also, when reading 16-bit from the area below GPD start, only the values at offsets 0x0000 (stack size), 0x0008 (CLT start address), 0x000c (command buffer start address) and 0x000e (command buffer size) are guaranteed to be populated by the runtime in big-endian, all others will appear in the host endian byte order so the program must not rely on their values in any way. For GPD area start address, better use `G` instruction exclusively. - Equi is strictly case-sensitive: all uppercase basic Latin letters, as well as a number of special characters, are reserved for machine instructions, and all custom words must be defined in lowercase only (additionally, `_` character is allowed in the identifiers). Within comments (see below), any characters can be used. All whitespace characters (space, tabulation, CR or LF) are discarded in Equi upon loading the program and can be used for code clarity any way the author wants.