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.

Sign up for GitHub

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

Jump to bottom

DEBUG: Step inside function calls (command “step”) #352

Closed
2 tasks done
PokhodenkoSA opened this issue May 11, 2021 · 4 comments
Closed
2 tasks done

DEBUG: Step inside function calls (command “step”) #352

PokhodenkoSA opened this issue May 11, 2021 · 4 comments
Assignees
@1e-to
Labels
debug Related to #149
Milestone
0.15.0

Comments

@PokhodenkoSA
Copy link
Contributor

PokhodenkoSA commented May 11, 2021 •
edited by akharche
Loading

We can not debug nested functions.
Check where debug info missed.
Investigate how to receive debug info on each step of pipeline.

Collected info about steps will help to write docs about compilation pipeline #385.
@PokhodenkoSA PokhodenkoSA mentioned this issue May 11, 2021
Open
36 tasks
@PokhodenkoSA
Copy link
Contributor Author

PokhodenkoSA commented Jun 2, 2021 •
edited by 1e-to
Loading

Investigating LLVM IR dump info #420

@1e-to
Copy link
Contributor

1e-to commented Jun 2, 2021

Spirv investigation: #418

@1e-to
Copy link
Contributor

1e-to commented Jun 2, 2021

Investigating IGC generated kernel binary #419

This was referenced Jun 3, 2021
Closed
Merged
@PokhodenkoSA
Copy link
Contributor Author

Implemented by #424

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@1e-to 1e-to

Labels
debug Related to #149
Projects
None yet
Milestone
0.15.0
Development

Successfully merging a pull request may close this issue.

Workaround for debugging nested functions 1e-to/numba
2 participants
@PokhodenkoSA @1e-to