sanitizer

Run NVIDIA compute-sanitizer (memcheck / racecheck / initcheck / synccheck). FIRST action on `INCORRECT_NUMERICAL` or flaky output — rolling back destroys the evidence; sanitizer often points at the exact line. Also useful for diagnosing race conditions in multi-block kernels and uninitialized-memory reads.

Ir para a instalação

Repositório: TongmingLAIC/AKO4X
Última atividade na origem: 31 de maio de 2026 às 08:57
Idioma detectado do SKILL.md: inglês
Estrelas: 67
Forks: 12

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/TongmingLAIC/AKO4X --skill sanitizer

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

2 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

bench

Run performance benchmarks to get a verdict on whether a kernel change actually helped. Use --ab-compare for sub-1x deltas (drift cancels in same container), --variance-check for noise floor, and the subset modes (--first, --smoke; --extremes is modal-backend only) for compile-correctness probes only — those are NOT performance verdicts. The only authoritative source for "is this change real". Benchmark specifics (config.toml schema, status enum, scoring formula, baseline rule, fresh-inputs contract) live in the `benchmark` skill.

2026-05-31

benchmark

Reference for the active benchmark harness — what it IS and how it behaves (the active benchmark is flashinfer-bench). Covers config.toml structure (`[solution]`/`[build]`/`[benchmark]` tables), the status enum, the workload / fresh-inputs model, reference-baseline + scoring mechanics, tolerance keys, TVM-FFI builder link limits, and the silent-skip cascade. Invoke whenever you decode a bench status string, hit an unfamiliar config.toml field, suspect "correctness passed but the headline is implausible", or need to know what's frozen before proposing a bench edit — do NOT guess field or status semantics. Bench commands and noise methodology (A/B compare, variance check, drift cancellation) live in the `bench` skill.

2026-05-31

cpp

Host-side C++ kernels (`[build].language = cpp`) — the `solution/{kernel.cpp, binding.py}` two-file TVM-FFI binding pattern, and when to reach for it (host-side orchestration of a kernel you write, or composing CUTLASS headers into it). Distinct from the `cuda` skill which covers `.cu` device kernels compiled by nvcc. Use when writing a host-side C++ kernel or deciding cpp-vs-cuda.

2026-05-31

Ver todas deste repositório

name	sanitizer
description	Run NVIDIA compute-sanitizer (memcheck / racecheck / initcheck / synccheck). FIRST action on `INCORRECT_NUMERICAL` or flaky output — rolling back destroys the evidence; sanitizer often points at the exact line. Also useful for diagnosing race conditions in multi-block kernels and uninitialized-memory reads.

Sanitizer

Wrapper around compute-sanitizer. Command entry: bash scripts/sanitize.sh.

Detailed reference: sanitizer.md. Top-level commands:

bash scripts/sanitize.sh --list
bash scripts/sanitize.sh --index 5                       # default: memcheck
bash scripts/sanitize.sh --index 5 --tool racecheck
bash scripts/sanitize.sh --index 5 --tool initcheck
bash scripts/sanitize.sh --index 5 --tool synccheck
bash scripts/sanitize.sh --index 5 --tool all            # sequential, separate timeout each

Key constraints

Run sanitizer FIRST on INCORRECT_NUMERICAL — before any rollback. Rolling back overwrites the failing kernel and destroys the only evidence of which line went wrong.
cuGetProcAddress_v2 noise inflates ERROR SUMMARY — these are PyTorch / triton / cupti probing optional CUDA driver entry points at import time. The wrapper's >>> NOISE FILTER <<< banner subtracts them; trust the "apparently-real kernel hits" count.
Real kernel errors always name a kernel / thread / block / address. If a hit only shows Python host frames, it's noise.
CUDA-graph-captured kernels show up but with sparse stack info; if traces are unhelpful, temporarily disable graph capture (env var or skip g.replay() path) for an eager-mode report, fix, then re-enable.

COUPLED references

Local backend: scripts/run_local_sanitize.py
Modal backend: scripts/run_modal_sanitize.py
Shared runtime: scripts/bench_utils.py (workload loading)

sanitizer

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

Sanitizer

Key constraints

COUPLED references

Sanitizer

Key constraints

COUPLED references