2 Commits

Include renames

Author	SHA1	Message	Date
AnachronautandClaude Opus 5	588e02aff5	Double CosmOS's half of the machine, and check that it fits ... The memory map gave CosmOS 0x0000 through 0x1FFF of Program Memory and applications 0x2000 and above. CosmOS is 8141 bytes at the previous commit, which is fifty one bytes short of the line, and the next thing added to it went over. GOING OVER DOES NOT FAIL WHERE IT HAPPENS. Nothing enforces the division: an application says where it goes with #Base and the loader puts it there, so a CosmOS that has grown past 0x1FFF simply has the next program loaded written over the end of it. What breaks is whichever part of the shell that program happened to cover, at whatever later moment somebody uses it. It turned up here as the monitor's assemble command answering "I do not know" to valid instructions, several commands into a session, on a machine that had booted perfectly well. Both halves are doubled: applications now start at 0x4000 in Program Memory and 0x2000 in Data Memory. That is 16K of code and 8K of data for the system, against the 8775 and 2948 it uses today. Both were on the same trajectory, and moving them together means the twenty files that say #Base are edited once rather than twice. The standalone loader's loadable.asm keeps its old base: it belongs to the loader CosmOS grew out of, not to CosmOS, and its addresses answer to a different program. The unbased-segment diagnostic keeps its old base too - it exists to produce an error message that names the address, and the message is what is recorded. Tests/docs.sh now reads the two limits out of the table in the README and measures both segments against them. It reads them rather than being told them because the table is the specification, and this is the second time in this project that the thing nobody checked is the thing that rotted. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E2JrLzFvuFX9fgi1LDRjrW	2026-08-24 22:21:02 -04:00
AnachronautandClaude Opus 5	dcb331c151	SplitBit assembles SplitBit: M1, a single file with no includes ... Programs/CosmOS/Assembler/ is an assembler written in SplitBit assembly. It runs under CosmOS, reads source off a SplitBit disk, and writes a binary back to it with no host involved anywhere: > run Asm.sbx hello.asm wrote hello.bin: program 17, data 14, labels 2 THE ACCEPTANCE TEST IS THE BYTES. Tests/native.sh assembles Programs/hello.asm both ways and compares the two files byte for byte, then runs the one the machine built. "It ran" and "the sizes look right" both pass for a binary with a label one byte out, which is a program that jumps into the middle of an instruction - so the only honest test is the one SplitDisk and sbfs.asm already work under: two implementations of one written specification, each checking the other. The files are identical and the result prints Hello, World! in 70 cycles. hello.asm is the target because it is the oldest program in the repository. The first thing this machine ever ran is now the first thing it assembles for itself. TWO PASSES OVER STREAMED SOURCE. The C assembler reads every token of every file into one array; that cannot port, because cosmos.asm alone is 56,047 bytes against 64K of Data Memory. The native one streams through a 256 byte window, twice, and keeps only the label table between the passes. Two passes suffice because every length is known without resolving anything - an instruction's from its shape, a value's is one, a string's is its characters and a zero - so the first pass fixes every address and the second never needs a fixup list. A forward reference stops being a special case and becomes the reason there are two passes at all. The parts, each checked before anything was built on it: source.asm characters out of a file of any size, with a line number token.asm tokens out of characters, one character of lookahead classify.asm what a token is, in the C assembler's order, which IS the language: keyword, instruction, value, string, label labels.asm names packed in an arena, four bytes of index each numbers.asm sixteen bit arithmetic, since sbfs.asm's cannot be reached table.asm the instruction set, generated by the same script the monitor's copy is, and now BOTH are checked by docs.sh readTest.asm and tokenTest.asm check the reader and the tokenizer on their own, recorded as cosmosSource and cosmosTokens. A wrong classification does not produce a wrong byte somewhere obvious; it produces a right looking program of the wrong length, so it is worth catching where it happens. WHAT IT REFUSES: #Include, #Base, #Align, #Reserve and #Vectors are refused by name rather than ignored. Skipping a directive would produce a file that looked right and was the wrong length, which is the worst thing an assembler can do. Two traps worth recording, both already known to this project and both hit again: CALL restores A, B and DP0-DP2, so three routines returning an answer in A had it undone by their own return; and numStep works on DP0, so three sites that set DP1 left a pointer that never advanced. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E2JrLzFvuFX9fgi1LDRjrW	2026-08-20 22:13:15 -04:00