compute-llk-bringup

Automate compute-kernel LLK shim implementation and integration in tt-emule.

4|1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/tenstorrent/tt-emule --skill compute-llk-bringup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compute-llk-bringup
Source: https://github.com/tenstorrent/tt-emule/tree/main/.claude/skills/compute-llk-bringup
Command: npx skills add https://github.com/tenstorrent/tt-emule --skill compute-llk-bringup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill addresses the complexity of bringing up missing compute-kernel LLK shims in the tt-emule environment, reducing manual effort and preventing ODR conflicts during JIT compilation.

Core Features & Use Cases

  • Standardized Shim Authoring: Provides a structured template-based approach to implementing missing compute ops, ensuring consistency with silicon APIs.
  • Automated Triage & Wiring: Integrates with project-specific tools to verify symbol existence, identify target paths, and handle necessary wiring in SFPU include headers.
  • Use Case: When a JIT compile error indicates a missing compute op, use this skill to systematically triage, implement, and verify the shim, ensuring it aligns with upstream LLK math and signatures.

Quick Start

Use the compute-llk-bringup skill to implement the missing tile operation for the specified compute kernel and wire it into the project structure.

Frequently Asked Questions about compute-llk-bringup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement missing compute-kernel LLK shims in the tt-emule emulator?

To implement missing compute-kernel LLK shims in the tt-emule emulator, use a structured template-based approach that mirrors upstream silicon API paths and ensures JIT compatibility. This automates triage, symbol verification, and automated index management.

Why does JIT compilation fail with ODR conflicts when adding compute operations?

JIT compilation fails with ODR conflicts due to mismanaged manual integration of compute operations. Standardizing compute-kernel LLK shim implementation prevents these issues by systematically verifying symbol existence and handling SFPU include header wiring.

What is the best way to triage missing compute ops during JIT compile errors?

The best way to triage missing compute ops during JIT compile errors is to integrate project-specific Python utilities that verify symbol existence, identify target paths, and handle necessary SFPU include header wiring automatically.

Does the compute-kernel shim bringup process support polynomial porting and signature verification?

Yes, the compute-kernel shim bringup process supports polynomial porting and signature verification. It systematically aligns new tile operations with upstream LLK math and signatures using project-specific Python utilities.

How do I wire a new tile operation into the SFPU include headers?

To wire a new tile operation into SFPU include headers, use automated triage tools that identify target paths and handle the necessary wiring. This ensures the compute-kernel LLK shim aligns with upstream silicon API paths.