and officially open-source

https://github.com/modular/modular/tree/main/KGEN

by relaxing delays for some small set of instructions we can get speed-up 0.2-0.3% for integer-heavy kernels

- ptxas has enough good heuristic

- in average you can reduce ~3% of stall counts

- overall speed up is not equivalent to the number of optimized stall counts

sorry if this is wrong sub-reddit for such questions

Are there some papers/experiments about subj to automatically derive things like indices swizzling/caching in shared memory/pinned memory etc?

https://redplait.blogspot.com/2026/07/identification-of-const-bank0-params.html

I don't have expensive monsters like sm100+ so extracted only params from maxler till hopper

https://redplait.blogspot.com/2026/06/re-of-ptx-grammar-from-ptxas-part-4.html

• names of all pseudo-instructions
• ptx ebnf grammar

You can recover tokens from compiled (f)lex code

Complexity for recovering of single token is O(T * log(T)) where T is size of yy_transition

details: https://redplait.blogspot.com/2026/06/recovering-tokens-from-flex-generated.html

https://redplait.blogspot.com/2026/06/re-of-ptx-grammar-from-ptxas-part-3.html

• revealing bodies of ptx pseudo instructions
• brute-force of (f)lex generated code to identify tokens

https://redplait.blogspot.com/2026/05/re-of-ptx-grammar-from-ptxas-part-2.html

• cicc unable to generate 42% of ptx instructions
• some of them are totally undocumented
• order of attributes is not important

https://redplait.blogspot.com/2026/05/re-of-ptx-grammar-from-ptxas.html

Project in active development, so if you are passionate on PTX, love digging into unstructured data and performing operations on sets, your help is welcomed

https://github.com/NVlabs/cuda-oxide

never used it but seems interesting

official nvidia link https://nvlabs.github.io/cuda-oxide/