Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More flexible debugging of triton IRs #223

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

copybara-service[bot]
Copy link

More flexible debugging of triton IRs

Printing triton IRs to stdout is easy but if there are multiple kernels involved
it's hard to tell which kernel corresponds to which IR. Instead we propose that
the user decides how to deal with the IRs by providing a callback and dealing
with the log however they want.

@google-cla
Copy link

google-cla bot commented Aug 23, 2023

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@copybara-service copybara-service bot force-pushed the test_559094543 branch 2 times, most recently from 6e72f9f to dfafb87 Compare August 24, 2023 09:29
Printing triton IRs to stdout is easy but if there are multiple kernels involved
it's hard to tell which kernel corresponds to which IR. Instead we propose that
the user decides how to deal with the IRs by providing a callback and dealing
with the log however they want.

PiperOrigin-RevId: 559094543
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants