-
Notifications
You must be signed in to change notification settings - Fork 114
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
Unable to create profile with create_llvm_prof - Empty profile map error #230
Comments
Can you drop the "DLLVM_BUILD_INSTRUMENTED=ON" flag? That shouldn't be necessary. Can you confirm that clang.baseline is the one obtained from the build step above? Also check that the binary was built with debug info. cc: @shenhanc78 can you take a look? Any ideas / tips to debug further? Thanks |
Looking at the error log again, since you are using a script to invoke perf multiple times, I think a build id is necessary to aggregate the samples correctly. Can you try building clang itself with an additional linker flag |
Yes, buildid is required. You may also use --ignore_build_id to skip this test. So all "clang" binary events (instead of only clang binary with the same buildid as recorded in perf.data file) in the perf will be processed. |
Thank you so much for your support! |
@snehasish after generating the profile, I'm feeding it through cmake using
I've tried every format among those supported by create_llvm_prof, but it doesn't seem to work. The first 10 lines of
|
Perhaps changing the option here [1] will be enough to pass the right flag to the compiler and linker. |
Thank you so much! |
Hi, I'm trying to compile clang using AutoFDO. In order, I'm running the following (adapted from the propeller script):
create_llvm_prof --binary $PATH_TO_BINARIES/clang.baseline --out baseline.prof
Everything succeeds, until the very last command which gives the following output:
I have tested several configurations and also tried to use different perf option, but the outcome does not seems to change.
Thanks in advance.
The text was updated successfully, but these errors were encountered: