compiler-development
Build NeverC or other LLVM compilers across frontend, IR, optimization, code generation, ABI, and target support. Use when the compiler pipeline is the subject; use narrower LLVM skills for isolated tooling or analysis.
Datos de origen
- Repositorio
- NeverSight/NeverC
- Última actividad en el origen
- 13 de septiembre de 2026 a las 11:17
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 96
- Forks
- 11
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Explorador de archivos
5 archivosMostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- compiler-development
- description
- Build NeverC or other LLVM compilers across frontend, IR, optimization, code generation, ABI, and target support. Use when the compiler pipeline is the subject; use narrower LLVM skills for isolated tooling or analysis.
# Compiler development
Use this skill when a change crosses compiler stages or target boundaries. Keep source-language semantics, LLVM IR, ABI lowering, object format, linker behavior, and runtime assumptions owned by the narrowest authoritative layer.
## Topic routing
Read only the reference that matches the work:
- [Targets and ABI](references/targets-and-abi.md) for platform matrices, calling conventions, build-system target handling, and module metadata.
- [DynCode and testing](references/dyncode-and-testing.md) for cross-platform DynCode invariants and target-specific verification.
- [Compiler pipeline](references/compiler-pipeline.md) for frontend, AST, IR generation, optimization, JIT, and language implementation patterns.
- [Workflow and resources](references/workflow-and-resources.md) for broader compiler-development workflow and upstream references.
For an isolated pass use `llvm-optimization`; for Clang/LLDB/LSP developer tooling use `llvm-tooling`; for static or dynamic analyses use their narrower skills. Prefer current NeverC source and repository documentation over examples in these references.
Ver en GitHub