When should I avoid using the 'export' keyword in tests?

You should avoid 'export' unless specifically testing export behavior, as it generates both masked and unmasked IR, which doubles the effort required for verification.

How should I name a regression test for a specific bug?

Following ISPC conventions, regression tests should be named after their GitHub issue number (e.g., 1234.ispc) to maintain clear traceability.

Why does this skill recommend using --nowrap?

The --nowrap flag prevents the ISPC compiler from inserting line breaks in long output strings, which ensures that FileCheck can reliably match patterns in the generated code.

What is the primary purpose of ISPC lit tests?

Lit tests in ISPC are used to verify compiler output (IR or assembly), validate diagnostic messages, and ensure cross-platform behavior remains consistent.

ISPC Lit Test Assistant

Name: ISPC Lit Test Assistant
Author: Microck

byMicrock

•

Security & Testing

Guides the creation of robust, portable, and efficient lit tests for the Intel Implicit SPMD Program Compiler (ISPC).

About

This skill provides specialized guidance for writing high-quality lit tests within the ISPC ecosystem, focusing on compiler correctness and regression prevention. It assists developers in implementing best practices such as utilizing the --nowrap flag for consistent FileCheck matching, optimizing test output with --nostdlib, and creating portable patterns that remain valid across various hardware targets and LLVM versions. Whether validating LLVM IR, assembly output, or diagnostic messages, this skill ensures that tests are minimal, documented, and properly categorized for the ISPC test suite.

Key Features

Standardized RUN command generation with optimal ISPC flags
Portable FileCheck pattern creation using named vector width variables
Target-specific test configuration with REQUIRES directives
81 GitHub stars
Intermediate IR inspection strategies using --debug-phase
Automated regression test naming conventions based on GitHub issues

Use Cases

Validating compiler diagnostics and warning messages for new features
Developing regression tests to lock in fixes for compiler bugs
Verifying platform-specific code generation across different SIMD architectures

About

Key Features

Standardized RUN command generation with optimal ISPC flags
Portable FileCheck pattern creation using named vector width variables
Target-specific test configuration with REQUIRES directives
81 GitHub stars
Intermediate IR inspection strategies using --debug-phase
Automated regression test naming conventions based on GitHub issues

Use Cases

Validating compiler diagnostics and warning messages for new features
Developing regression tests to lock in fixes for compiler bugs
Verifying platform-specific code generation across different SIMD architectures