pytorch - 💡(How to fix) Fix Native Operators with DSLs

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

New Feature for Release

Support for in-tree PyT operators written in DSLs like triton and cuteDSL

Point(s) of contact

slayton58, meta gchat

Release Mode (pytorch/pytorch features only)

In-tree

Out-Of-Tree Repo

No response

Description and value to the user

Provide infrastructure for developers to leverage the power, performance and ease-of-use of DSL-based languages like triton to write native operators in PyTorch.

Link to design doc, GitHub issues, past submissions, etc

No response

What feedback adopters have provided

No response

Plan for documentations / tutorials

Tutorial is not needed

Additional context for tutorials

No response

Marketing/Blog Coverage

Yes

Are you requesting other marketing assistance with this feature?

No response

Release Version

No response

OS / Platform / Compute Coverage

Only tested linux + GPU

Testing Support (CI, test cases, etc..)

CI tests

cc @ezyang @bhosmer @bdhirsh @kadeng @bobrenjc93

extent analysis

TL;DR

  • The feature implementation for supporting in-tree PyT operators written in DSLs like Triton and CuteDSL is likely complete, but additional steps are needed for release and testing.

Guidance

  • Verify that the CI tests cover all necessary scenarios for the new feature to ensure its stability and functionality.
  • Consider creating documentation or tutorials to help developers understand how to leverage the new feature, despite the initial statement that a tutorial is not needed, as it may be beneficial for adoption and user support.
  • Reach out to the points of contact (slayton58, meta gchat) for further guidance on the release process and any additional requirements.
  • Ensure that the feature is tested on multiple platforms, not just Linux + GPU, to guarantee broader compatibility.

Example

  • No specific code example can be provided without more details on the implementation, but ensuring that the CI tests are comprehensive is crucial.

Notes

  • The lack of information on release version, out-of-tree repo, and detailed testing support makes it challenging to provide a comprehensive fix or workaround.
  • The feature's compatibility and performance on different operating systems and compute environments should be thoroughly evaluated.

Recommendation

  • Apply workaround: Given the information provided, it seems that while the feature itself might be implemented, there are gaps in testing, documentation, and potentially release planning. Therefore, applying a workaround such as enhancing testing coverage and considering user documentation could be beneficial until a more comprehensive solution is available.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

pytorch - 💡(How to fix) Fix Native Operators with DSLs