Skip to content

[KMCompiler] fix performance regression caused by explicit annotate constexpr value as int#648

Open
zhongsanming wants to merge 1 commit into
flagos-ai:triton_v3.6.xfrom
zhongsanming:fix-type-annotation-performance-regression
Open

[KMCompiler] fix performance regression caused by explicit annotate constexpr value as int#648
zhongsanming wants to merge 1 commit into
flagos-ai:triton_v3.6.xfrom
zhongsanming:fix-type-annotation-performance-regression

Conversation

@zhongsanming
Copy link
Copy Markdown

@zhongsanming zhongsanming commented Jun 4, 2026

fix a performance issue introduced upstream triton, where an explicit type annotation of : int will overwrite constexpr when generating code, which further cause the coalesce pass failed to generate optimized IR.

This affect all triton version starting from 3.4, and most of the op in FlagGems repo.

See also:

triton-lang/triton#9834

triton-lang/triton#6152

@zhongsanming zhongsanming requested a review from zhzhcookie as a code owner June 4, 2026 02:03
@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Jun 4, 2026

CLA assistant check
All committers have signed the CLA.

@zhongsanming zhongsanming changed the title [KMPL] fix performance regression caused by explicit annotate constexpr value as int [KMCompiler] fix performance regression caused by explicit annotate constexpr value as int Jun 4, 2026
@zhongsanming zhongsanming force-pushed the fix-type-annotation-performance-regression branch from 7605489 to 97b9334 Compare June 4, 2026 02:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants