triton-ascend-api-rules

Forbidden syntax in Triton Ascend kernels includes return, break, continue, lambda, and direct tensor indexing. Banning these constructs prevents unsafe compilation and runtime failures on Ascend hardware.

Use mask-based control flow and safe tl.where operations instead of break or continue statements. This approach enforces predictable execution paths and prevents runtime failures during Ascend compilation.

Yes, constexpr usage is mandated for Triton Ascend kernel compilation on Atlas A2 backends. Enforcing compile-time evaluation of specific variables ensures safe compilation and predictable execution.

Direct tensor indexing fails compilation because the Triton Ascend hard rules explicitly disallow it. This static prohibition prevents unsafe memory access patterns and ensures predictable execution on Ascend backends.

Lambda expressions are strictly prohibited in Triton Ascend kernels. This limitation prevents unsafe syntax constructs that could cause unpredictable compilation or runtime failures on Ascend hardware.