Function.RawBranchCount is initialized for fdata profile but not for yaml one.
The diff adds the computation of the field for yaml profiles
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Is that primarily needed for "X out of Y samples in the binary (Z%) belong to functions with invalid (possibly stale) profile" log message? Can you add a test using yaml profile, e.g. based on bolt/test/X86/pre-aggregated-perf.test?
Comment Actions
I noticed a few (minor) differences between how yaml and fdata profiles are parsed and processed -- this is one of them and can easily be fixed. I will add a test.
Comment Actions
- re-enabled test in branch-data.test
- added a check to the test verifying the new flag