Daniel Samson
e2dddc941f
The "fs.base" spelling read like a field/submodule access, but no such
identifier exists — it meant the x86_64 FS segment base (the IA32_FS_BASE
MSR). Two problems fixed:
- Arch-neutrality: in generic docs, the runtime, and the plan, the mechanism
is now named by its arch-neutral concept — the "thread pointer" — matching
the already-renamed `thread_pointer` Task field, `set_thread_pointer`
syscall, and `architecture.setThreadPointer` fn. x86-specific spots keep
the precise names: `IA32_FS_BASE` (the MSR), `%fs:8`/`%fs:0`, variant-II.
- Stale identifiers: the M10 section in threading-plan.md still referenced
`fs_base` on Task and `architecture.setFsBase` — both renamed away in the
arch-neutral pass. Corrected to `thread_pointer` / `setThreadPointer`.
The x86-only `thread-tls` test (which really does write `%fs:8`) now says
"FS base" (no dot) consistently, matching the established form already in
tests.zig. The matched serial markers ("thread-tls: ok" / "thread-tls:
FAIL") are unchanged; only a non-load-bearing FAIL parenthetical was
reworded.
Verified: zig build clean, thread-tls passes.
|
||
|---|---|---|
| .. | ||
| block.zig | ||
| device.zig | ||
| display.zig | ||
| dma.zig | ||
| fs.zig | ||
| heap.zig | ||
| input.zig | ||
| ipc.zig | ||
| process.zig | ||
| root.zig | ||
| runtime.zig | ||
| service.zig | ||
| shm.zig | ||
| start.zig | ||
| system-call.zig | ||
| system.zig | ||
| thread.zig | ||
| time.zig | ||
| usb.zig | ||
| user.ld | ||