[all-commits] [llvm/llvm-project] 229ca7: [memprof] Report an error when buildid and profile...

[zcfh via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 229ca7dbcb5a6bcbcdc87fb0feb29362375c2843
      https://github.com/llvm/llvm-project/commit/229ca7dbcb5a6bcbcdc87fb0feb29362375c2843
  Author: zcfh <1412805291 at qq.com>
  Date:   2025-04-03 (Thu, 03 Apr 2025)

  Changed paths:
    M llvm/lib/ProfileData/MemProfReader.cpp
    M llvm/test/tools/llvm-profdata/memprof-buildid.test

  Log Message:
  -----------
  [memprof] Report an error when buildid and profile do not match (#132504)

## Problem
When the build ids of the profile and binary do not match, the error
reported by llvm-profdata is `no entries in callstack map after
symbolization`, but the root cause of this problem is the **build id
mismatch**.
## Trigger scenario
For example, when performing `memprof` optimization on `clang`,
`rawprofile` is collected through `ninja clang`. In addition to running
clang, some other programs will also be executed, and these programs
will also generate rawprofile. When `no entries in callstack map after
symbolization` appears during `llvm-profdata merge`, users may
mistakenly think that the **instrumentation failed or other reasons**,
and will **not directly realize that the binary and profile do not
match**.

## Changed
Currently, when the build id does not match, an assert error is
triggered only in debug mode. Change it to directly return an error when
the build id does not match.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications