When no --profiled-binary flag is provided we can print out the build
ids of the modules in the profile. This can help the user fetch the
correct binary from e.g. remote object store.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Thanks for the quick review!
llvm/lib/ProfileData/RawMemProfReader.cpp | ||
---|---|---|
204 | Opted to document the param since I don't think printing the profile path is useful (the binary path is unset). | |
542 | If we keep them in order then the profiled binary build id *should* be the first entry in this list. We rely on the sanitizer tooling (which calls dl_iterate_phdr [1]) to maintain the order which is read from the program headers and we preserve the order in the profile. Added a short comment. "The first object visited by callback is the main program." |
lgtm
llvm/lib/ProfileData/RawMemProfReader.cpp | ||
---|---|---|
542 | Thanks for the clarification. I would just add the man page link and excerpt to the comment to document why it should be first. |
Should we pass the Path instead of "" for the report() Context parameter? If not useful, probably document the constant "" parameter.