-
Notifications
You must be signed in to change notification settings - Fork 14
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
Added LOC info to TTRT Perf output #1401
Conversation
|
||
mlir::OpPrintingFlags flags; | ||
flags.enableDebugInfo(); // Enable the loc dumping | ||
module->print(os, flags); | ||
|
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.
Printing the MLIR module with debug info into the flatbuffer. I'm not sure if this is the behavior we want, but it could be useful to show the locations that are being propagated in the results.
42856e7
to
02b2425
Compare
Not merging in due to some weird quirk where this PR causes |
30a3a81
to
06c8ffe
Compare
Fixed! Will merge in on green check. |
FYI @ctodTT, I think this |
thanks @vprajapati-tt ! This looks great. One comment inlined |
|
||
from ttrt.common.util import * | ||
from ttrt.common.query import Query | ||
|
||
|
||
def get_loc_data_hook(binary, programContext, opContext): | ||
op_debug_str = ttrt.runtime.get_op_debug_str(opContext) |
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.
I'm assuming we aren't using the hook to get the loc info, but just querying the Tracy message itself? Since this function is not called anywhere.
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 keeps getting rebased in oh my god that's super annoying. I'll add a branch to drop it.
ops_perf_results.csv
artifact.