I added just enough to allow us to see a top-level breakdown of time taken. This
is the result of loading the time-trace output into chrome:://tracing:
Details
- Reviewers
oontvoo - Group Reviewers
Restricted Project - Commits
- rG4bcaafeb0e82: [lld-macho] Add more TimeTraceScopes
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
lld/MachO/Driver.cpp | ||
---|---|---|
1069–1080 | It's kind of silly that this takes a non-trivial amount of time. Perhaps that's where a chunk of the speedup in D98837 is coming from. Maybe once that lands we can remove this TimeTraceScope block. cc @alexshap |
lld/MachO/Driver.cpp | ||
---|---|---|
997–998 | Do you want to move these two into the createFiles() too? | |
lld/MachO/Writer.cpp | ||
953–954 | Could this be moved to cover the whole function? I see the finalize*() functions have their own time-sccopes. Similarly, the write*() have theirs too. |
Do you want to move these two into the createFiles() too?