debug-flydsl-kernel

Diagnose incorrect FlyDSL GPU kernel outputs, NaNs, infs, and crashes.

260|104|Updated Nov 23, 2025
One-click install
npx skills add https://github.com/ROCm/FlyDSL --skill debug-flydsl-kernel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-flydsl-kernel
Source: https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/debug-flydsl-kernel
Command: npx skills add https://github.com/ROCm/FlyDSL --skill debug-flydsl-kernel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug FlyDSL GPU kernels that produce NaN, inf, or incorrect results, or crash, by providing structured diagnostics and reproducible workflows.

Core Features & Use Cases

  • Diagnostic workflows for cache invalidation, tracing pitfalls (runtime conditionals, range vs range_constexpr), and scf.for state packing.
  • MFMA operand layout verification, LDS bank conflict diagnosis, and host-side tensor inspection to pinpoint layout and addressing issues.
  • Real-world use cases include isolating defects in single-partition and multi-partition kernels, validating outputs, and ensuring robust kernel behavior.

Quick Start

Run the FlyDSL kernel debugger on the target kernel to reproduce the issue and collect diagnostics.

Frequently Asked Questions about debug-flydsl-kernel

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

FAQPage Schema
How do I debug FlyDSL GPU kernels that produce NaN or inf outputs?

To debug FlyDSL GPU kernels producing NaN or inf outputs, run the debugger to collect structured diagnostics and reproduce the issue. It identifies incorrect results through cache invalidation checks and host-side tensor inspection.

Why does my FlyDSL GPU kernel crash during scf.for loops?

FlyDSL GPU kernel crashes during scf.for loops often stem from incorrect state packing. The debugger provides targeted diagnostics for scf.for state packing to isolate the defect and ensure robust kernel behavior.

What is the difference between range and range_constexpr in FlyDSL tracing?

In FlyDSL tracing, range and range_constexpr differ in how runtime conditionals are handled. The debugger traces these pitfalls to identify incorrect kernel outputs and validate partition handling.

Can I diagnose LDS bank conflicts and MFMA operand layout issues in FlyDSL?

Yes, you can diagnose LDS bank conflicts and verify MFMA operand layout in FlyDSL. The debugger pinpoints addressing and layout issues to resolve incorrect GPU kernel computations.

Does the FlyDSL debugger support multi-partition GPU kernel isolation?

Yes, the FlyDSL debugger supports multi-partition GPU kernel isolation. It provides diagnostic workflows to isolate defects in both single-partition and multi-partition kernels and validate their outputs.