CLI & Workflows

This page collects the commands most useful while working on the Semantic/native compiler pipeline.

Stable object runner

START-HERE.bat

Runs the normal per-unit object build.

START-FAST-5S.bat

Short diagnostic pass. Useful for quickly finding deterministic compiler failures, but large units may legitimately timeout.

RETRY-120S.bat

Retries failed/slow units with a larger hard timeout.

STATUS.bat

Prints the current unit/object summary.

MAKE-REPORT.bat

Collects statuses, errors and object paths into a report.

CLEAN.bat

Removes generated build state so the next run starts cleanly.

Semantic transport examples

Documented Semantic CLI flows include patterns such as:

semantic-export -source go input.go -format sp -o program.sp
semantic-transpile -target rust program.sp -o output.rs
semantic-convert program.json -o program.sp
semantic-format program.sp -o formatted.sp
semantic-validate program.sp
semantic-info program.sp

Module examples

CodeTranspiler.exe semantic module import path\to\package
CodeTranspiler.exe semantic module import --language go path\to\main.go
CodeTranspiler.exe semantic module list
CodeTranspiler.exe semantic module verify <cache-key>

Selfhosting target commands

The eventual native user-facing flow should be as simple as:

msplc.exe msplc-selfhost.se stage2.exe
stage2.exe msplc-selfhost.se stage3.exe

The debug object runner is an engineering aid on the path to that interface.

SWC command line

The current native Windows compiler is called swc and is distributed as swc.exe.

swc version
swc help
swc compile <input.se|input.sp|input.spz|input.json|input.smod> -o <output.exe> [--embed-all|--embed-needed|--no-modules]

The SWC source, matrix, reader, module units, tests, and release package are maintained in the mwsplc repository. The complete rich-UAST machine-code emitter is still being expanded, so generated output must be checked for real runtime behavior.