ispc-lit-tests

ISPC lit tests should use portable check patterns, enforce --nowrap and --nostdlib flags, avoid export unless testing specific export behavior, specify exact targets and features with REQUIRES directives, and document test intent and expected outcomes for regression and diagnostic validation.

Structure portable ISPC lit tests by organizing checks that verify compiler output and diagnostics across platforms, using platform-agnostic patterns, specifying target requirements upfront, and documenting expected results so tests validate code generation consistently.

Use lit tests for ISPC when validating compiler diagnostics, regression coverage, and code-generation behavior across different targets and platforms. They verify that compiler output matches expected results and catch platform-specific behavioral differences.

Yes, lit tests validate ISPC code generation by checking compiler output against expected results with portable patterns. They verify functional requirements, platform behavior, and catch regressions in generated code across specified targets and features.

Include --nowrap and --nostdlib flags when testing ISPC to isolate test scope. Avoid export unless specifically testing export functionality, use REQUIRES to specify exact targets and features, and employ portable checks to ensure consistent validation across platforms.

Lit tests catch ISPC regressions by enforcing portable check patterns that verify compiler output consistency across platforms and target configurations. They document expected outcomes and validate that code generation, diagnostics, and platform behavior remain stable across changes.