Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

spice-dump

Sterne86

Forks5

Aktualisiert31. Mai 2026 um 23:53

Dump compiler intermediate output (LLVM IR, assembly, AST, CST, symbol table, types) for a Spice source or test-input file using the `spice` CLI dump flags. Use when the user wants to inspect what the compiler generates for a `.spice` file, debug codegen, or regenerate reference dumps.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

spicelang

spicelang/spice

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	spice-dump
description	Dump compiler intermediate output (LLVM IR, assembly, AST, CST, symbol table, types) for a Spice source or test-input file using the `spice` CLI dump flags. Use when the user wants to inspect what the compiler generates for a `.spice` file, debug codegen, or regenerate reference dumps.

Dump Spice compiler output

The spice compiler (built at cmake-build-debug/src/spice, see the spice-build skill) can dump every stage of compilation via flags on the build / run / test subcommands.

Quick start

SPICE=cmake-build-debug/src/spice

# Dump LLVM IR for a source file (unoptimized)
$SPICE build -O0 -ir path/to/source.spice

# Dump assembly
$SPICE build -O0 -s path/to/source.spice

# Inspect IR for an existing test input
$SPICE build -O0 -ir test/test-files/irgenerator/for-loops/success-for-loop/source.spice

Many test-case dirs reference IR at -O2/-O3 — pass the matching opt level to reproduce those (e.g. -O2 -ir to compare against ir-code-O2.ll).

Dump flags (build / run / test subcommands)

Flag	Aliases	Dumps
`--dump-cst`	`-cst`	Concrete syntax tree (serialized + SVG)
`--dump-ast`	`-ast`	Abstract syntax tree (serialized + SVG)
`--dump-symtab`		Serialized symbol tables
`--dump-types`		All used types
`--dump-ir`	`-ir`	LLVM IR
`--dump-assembly`	`-asm`, `-s`	Assembly
`--dump-object-file`		Object files
`--dump-dependency-graph`		Compile-unit dependency graph
`--dump-cache-stats`		Internal lookup-cache stats

Control flags (build subcommand):

--dump-to-files — write dumps to files instead of stdout.
--abort-after-dump — stop after the first requested dump (skip the rest of compilation/linking). Handy for fast IR/AST inspection without producing a binary.

Useful companions:

Optimization: -O0/-O1/-O2/-O3/-Os/-Oz (IR/asm differ per level).
-d / --debug-output — verbose compiler debug output.
--target, --target-arch, --target-os — cross-target IR/assembly (e.g. assembly refs are kept per target like assembly-linux-aarch64.asm).
--build-mode test -ir (or the test subcommand) — dump IR for the test harness variant of a file.

Common recipes

SPICE=cmake-build-debug/src/spice
SRC=test/test-files/irgenerator/for-loops/success-for-loop/source.spice

# Just the IR, nothing else, fast
$SPICE build -O0 -ir --abort-after-dump $SRC

# IR at O2 (matches ir-code-O2.ll references)
$SPICE build -O2 -ir --abort-after-dump $SRC

# AST + CST as SVG/text
$SPICE build -ast -cst --abort-after-dump $SRC

# Symbol table and type registry
$SPICE build --dump-symtab --dump-types --abort-after-dump $SRC

# Cross-target assembly
$SPICE build -O2 -s --target-arch aarch64 --target-os linux --abort-after-dump $SRC

Relation to reference tests

The dump filenames above correspond to reference files in test/test-files/<group>/<case>/ (e.g. ir-code.ll, ir-code-O2.ll, assembly-linux-amd64.asm, symbol-table.json, type-registry.out, syntax-tree.dot). To regenerate those en masse after an intended compiler change, prefer spicetest --update-refs (see the spice-test skill) rather than hand-copying dumps. Use the manual dumps here for ad-hoc inspection and debugging of a single file.

Run $SPICE --help (or $SPICE build --help) to see the full, current option list.

Mehr aus diesem Repository

gleiches Repository

spice-build

spicelang/spice

Build the Spice compiler (`spice`) and/or the test runner (`spicetest`) with CMake/Ninja. Use when the user wants to compile/rebuild the project, build a specific target, produce a release/debug build, or set up the CMake build directory before running or testing.

2026-06-2486

spice-contribute

spicelang/spice

Guidelines for contributing changes to the Spice GitHub repository — branch naming conventions, commit message format, PR workflow, no-push-to-main rule, and quality gates. Use when preparing a branch for review, writing a commit, opening a PR, or checking that a contribution is ready to merge.

2026-06-0786

spice-profiling

spicelang/spice

Profile and benchmark the Spice compiler (the host C++ `spice` program) and the native binaries it emits from `.spice` files — using the built-in per-stage timers, the dedicated CMake profiling build options, and external tools (perf, valgrind/callgrind, flamegraph, hyperfine). Covers the preferred build/compile settings for representative profiling of each layer. Use when the user wants to find where compile time or runtime is spent, benchmark a change, or chase a performance regression.

2026-06-0186

spice-debugging

spicelang/spice

Find, diagnose, and fix bugs in the Spice compiler or in a compiled Spice program using GDB, objdump, sanitizers (for both the host C++ compiler and the emitted Spice program via the built-in `--sanitizer` flag), the compiler dump flags, and valgrind. Use when investigating a crash, miscompilation, memory error, or undefined behavior, or when triaging a failing test. Whenever a bug is fixed, this skill also requires extending or adding a test that covers the problematic code path and any related uncovered paths.

2026-06-0186

spice-add-test

spicelang/spice

Add a reference/integration test case under test/test-files for the Spice compiler. Covers the directory layout (flat vs grouped suites), the exact reference filenames the runner compares against, control/skip marker files, platform-specific variants, and the --update-refs workflow to generate expected output. Use when adding or modifying compiler test cases.

2026-06-0186

spice-architecture

spicelang/spice

Orientation map of the Spice compiler codebase — the compilation pipeline (lexer → parser → CST → AST → import collector → symbol table → type checker → IR generator → optimizer → object emitter → linker), the key class/file for each stage, and the SourceFile orchestration sequence. Use when navigating the compiler, deciding where a change belongs, or understanding how a stage feeds the next.

2026-06-0186

name	spice-dump
description	Dump compiler intermediate output (LLVM IR, assembly, AST, CST, symbol table, types) for a Spice source or test-input file using the `spice` CLI dump flags. Use when the user wants to inspect what the compiler generates for a `.spice` file, debug codegen, or regenerate reference dumps.

Dump Spice compiler output

The spice compiler (built at cmake-build-debug/src/spice, see the spice-build skill) can dump every stage of compilation via flags on the build / run / test subcommands.

Quick start

SPICE=cmake-build-debug/src/spice

# Dump LLVM IR for a source file (unoptimized)
$SPICE build -O0 -ir path/to/source.spice

# Dump assembly
$SPICE build -O0 -s path/to/source.spice

# Inspect IR for an existing test input
$SPICE build -O0 -ir test/test-files/irgenerator/for-loops/success-for-loop/source.spice

Many test-case dirs reference IR at -O2/-O3 — pass the matching opt level to reproduce those (e.g. -O2 -ir to compare against ir-code-O2.ll).

Dump flags (build / run / test subcommands)

Flag	Aliases	Dumps
`--dump-cst`	`-cst`	Concrete syntax tree (serialized + SVG)
`--dump-ast`	`-ast`	Abstract syntax tree (serialized + SVG)
`--dump-symtab`		Serialized symbol tables
`--dump-types`		All used types
`--dump-ir`	`-ir`	LLVM IR
`--dump-assembly`	`-asm`, `-s`	Assembly
`--dump-object-file`		Object files
`--dump-dependency-graph`		Compile-unit dependency graph
`--dump-cache-stats`		Internal lookup-cache stats

Control flags (build subcommand):

--dump-to-files — write dumps to files instead of stdout.
--abort-after-dump — stop after the first requested dump (skip the rest of compilation/linking). Handy for fast IR/AST inspection without producing a binary.

Useful companions:

Optimization: -O0/-O1/-O2/-O3/-Os/-Oz (IR/asm differ per level).
-d / --debug-output — verbose compiler debug output.
--target, --target-arch, --target-os — cross-target IR/assembly (e.g. assembly refs are kept per target like assembly-linux-aarch64.asm).
--build-mode test -ir (or the test subcommand) — dump IR for the test harness variant of a file.

Common recipes

SPICE=cmake-build-debug/src/spice
SRC=test/test-files/irgenerator/for-loops/success-for-loop/source.spice

# Just the IR, nothing else, fast
$SPICE build -O0 -ir --abort-after-dump $SRC

# IR at O2 (matches ir-code-O2.ll references)
$SPICE build -O2 -ir --abort-after-dump $SRC

# AST + CST as SVG/text
$SPICE build -ast -cst --abort-after-dump $SRC

# Symbol table and type registry
$SPICE build --dump-symtab --dump-types --abort-after-dump $SRC

# Cross-target assembly
$SPICE build -O2 -s --target-arch aarch64 --target-os linux --abort-after-dump $SRC

Relation to reference tests

Run $SPICE --help (or $SPICE build --help) to see the full, current option list.