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

[Frontend] Add TRITON_DEV_MODE for easier debugging of frontend errors #4683

Merged
merged 2 commits into from
Sep 10, 2024

Conversation

peterbell10
Copy link
Contributor

Currently triton filters out parts of the stack trace that come from inside the compiler itself which is great for not confusing users. However this adds the ability to disable it by setting TRITON_DEV_MODE=1 in the environment (open to bikeshedding on the name) for when you're trying to debug the frontend itself.

Currently triton filters out parts of the stack trace that come from
inside the compiler itself which is great for not confusing users.
However this adds the ability to disable it by setting
TRITON_DEV_MODE="1" in the environment.
@ThomasRaoux
Copy link
Collaborator

Seems very convenient! In term of naming bikeshed I wonder if it should be more of TRITON_AST_DEBUGGING or TRITON_FRONT_END_DEBUGGING?

@peterbell10 peterbell10 enabled auto-merge (squash) September 9, 2024 23:53
@peterbell10 peterbell10 merged commit 2df33bb into main Sep 10, 2024
7 checks passed
@peterbell10 peterbell10 deleted the pb/triton-dev-mode branch September 10, 2024 00:01
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.

2 participants