-
Notifications
You must be signed in to change notification settings - Fork 21
Frozen Functions Kernel History #153
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks nice, good job catching that this was missing!
src/record_ts.cpp
Outdated
} | ||
|
||
state.kernel_history.append(kernel_history_entry); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If all of this code that creates the kernel history entry is very close to the existing code (in the normal kernel launch function), would it make sense to factor some of this out to a common function?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it make sense for the llvm/cuda threadstate to record the kernel history entry? This is how it is recorded for other operations, such as reductions etc.
d6724b0
to
039b0e8
Compare
039b0e8
to
f043eda
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a minor typography comment :)
Enables frozen functions to generate kernel history entries, when replaying kernels.