The assembler can say where everything ended up
-S writes every label and the address it was given, in address order. Nothing else knows that. A program on the disk is bytes; the monitor can disassemble it but has no idea what any of it is called. So counting which addresses a program calls says a great deal and names nothing - the answer arrives as a column of numbers and somebody works out by hand which routine each one is inside. It was deferred when the native assembler was planned, as a listing and symbol dump nobody needed yet. Finding out where the assembler spends its time is what needed it: the top six call targets were addresses until this existed and are numStep, numCompare, tokGet, srcNext, numAddByte and clsSameName with it. Sorted by address rather than by name, because the question asked of it is always "what is at this address". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E2JrLzFvuFX9fgi1LDRjrW
This commit is contained in:
co-authored by
Claude Opus 5
parent
af0360128b
commit
19ab36a201
@@ -105,8 +105,14 @@ If the CPU reads a byte that is not an instruction, it goes to the fault handler
|
||||
| `-o <file>` | Write the output to this path. |
|
||||
| `-I <dir>` | Look in this directory for included files. May be given more than once. |
|
||||
| `-M <file>` | Write out which source files the output depends on, as a make rule. |
|
||||
| `-S <file>` | Write every label and the address it was given, in address order. |
|
||||
| `-h`, `--help` | Show help and usage information. |
|
||||
|
||||
`-S` is the only thing that knows what a program's addresses are called. A program on the
|
||||
disk is bytes; the machine's own monitor can disassemble it but has no idea what any of it
|
||||
is named. So a count of which addresses get called says a great deal and names nothing, and
|
||||
this is what turns such a count into a list of routine names.
|
||||
|
||||
Without `-o` the output takes the source file's name, in the directory you called the assembler from, with the extension the format asks for: `.bin` for a boot image and `.sbx` for a loadable program. Included files are looked for beside the file that includes them, and then along the directories given with `-I`.
|
||||
|
||||
## Managing Disks: SplitDisk
|
||||
|
||||
Reference in New Issue
Block a user