tlopex opened a new pull request, #19838:
URL: https://github.com/apache/tvm/pull/19838

   PR #19677 registered every CUDA / Trainium device intrinsic under two Op 
names: a flat `tirx.<ns>_<name>` alias plus the canonical `tirx.<ns>.<name>`. 
The flat aliases were a migration shim; passes and codegen that match an 
intrinsic had to check both spellings (the dual-name IsOp pattern). The Python 
builders and TVMScript parser already canonicalize, so every real Call already 
carries the canonical op and the flat aliases were dead weight.
   
   This pr removes the flat device-intrinsic aliases, keeping only the 
canonical namespaced ops:
   
   - RegisterDeviceIntrinsic (backend/cuda) and RegisterNKIIntrinsic 
(backend/trn) register only the canonical name.
   - Drop the flat-only macro registrations for device intrinsics; the 
canonical op with all attrs is registered from the alias table. The WMMA 
tvm_*_sync / mma_store / mma_fill builtins and the profiling timer_*_cuda 
builtins keep their flat names (no namespace / canonical form, category 
"builtin").
   - Remove the redundant flat tirx.ptx_fetch_register registration.
   - C++ consumers that resolved a flat op by name string now use the canonical 
name; the ptx_elect_sync / cuda_func_call dual-name matchers collapse to the 
canonical check.
   - Python: the InjectPTXAsyncCopy round-trip Op.get and the matching test 
assertion use the canonical name. call_intrin keeps its flat->canonical rewrite 
for back-compat, so user-facing wrappers are unchanged.
   - test_op_namespace_cleanup asserts device_intrin op names are canonical so 
a flat alias cannot silently reappear.
   
   Generated CUDA is byte-identical: helper names are literals and codegen 
dispatches by op name, with the registry resolving the canonical name to the 
same helper.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to