Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microck/ispc-lit-tests
Best practices for creating ISPC lit tests.
Passed 22 of 22 test cases with the skill, and 15 of 22 without it.
and 11 more in the full report
7 fixed15 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
When running compiler tests, long assembly lines get wrapped in stderr/stdout, breaking FileCheck string matching. Which ISPC flag prevents output line wrapping?
| Checked | Without skill | With skill |
|---|---|---|
| The response recommends using the --nowrap flag. | Missed | Passed |
The instructions your model reads when the skill loads.
A concise guide for writing lit tests for the ISPC. These tests ensure compiler correctness, verify generated code, and prevent regressions.
Use lit tests when validating:
--nowrapPrevents line wrapping in compiler output for consistent FileCheck matching:
// RUN: %{ispc} %s --target=host --nowrap --emit-llvm-text -o - | FileCheck %s
--nostdlib When Not Testing Library CodeSimplifies test output and avoids unrelated symbols:
// RUN: %{ispc} %s --target=host --nostdlib --nowrap -o - | FileCheck %s
export Unless Testing Itexport functions generate both masked and unmasked IR — doubling the verification effort.
// Preferred
void foo() { ... }
test cases passed, vs 15 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.