andrius
/
stage0
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update documentation to reflect implementation changes in stage0 lisp

This commit is contained in:
Jeremiah Orians 2017-05-14 14:45:10 -04:00
parent a8360e1b4f
commit 24d67b3810
No known key found for this signature in database
GPG Key ID: 7457821534D2ACCD
2 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
CHANGELOG.org
View File

@ -27,6 +27,7 @@ Converted stage2 lisp implementation from dynamic scope to Lexical
** Fixed ** Fixed
Made Web debugger provide more useful information Made Web debugger provide more useful information
Fixed regression in web debugger's ability to read input files Fixed regression in web debugger's ability to read input files
Fixed SHA256SUM of stage2 lisp to match new binary result
** Removed ** Removed

2
bootstrapping Steps.org
View File

@ -144,7 +144,7 @@ Then we use our M0 Line macro assembler to convert our assembly into hex2 format
Then we need to assemble that hex into our desired program: Then we need to assemble that hex into our desired program:
./bin/vm --rom roms/stage1_assembler-2 --tape_01 temp2 --tape_02 roms/lisp --memory 48K ./bin/vm --rom roms/stage1_assembler-2 --tape_01 temp2 --tape_02 roms/lisp --memory 48K
roms/lisp should have the sha256sum of 48a615b911e167d72b2ed42e1ef9db19f32555bfce5657904ceeaca46716d48f roms/lisp should have the sha256sum of 862a1ecfef7c670a1231a0c3ff117bf05e683ea0e5d80fc5f195a3b251d8b598
Our lisp will first attempt to evaluate any code in tape_01 and then evaluate any code that the user types in. Our lisp will first attempt to evaluate any code in tape_01 and then evaluate any code that the user types in.
It is recommended to run with no less than 4MB of Memory It is recommended to run with no less than 4MB of Memory