maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/compiler-rt/test/profile/instrprof-lto-pgogen.c

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

15 lines
492 B
C
Raw Normal View History

[profile][test] Add -fuse-ld=bfd to make instrprof-lto-pgogen.c robust Otherwise if 'ld' is an older system LLD (FreeBSD; or if someone adds 'ld' to point to an LLD from a different installation) which does not support the current ModuleSummaryIndex::BitCodeSummaryVersion, the test will fail. Add lit feature 'binutils_lto'. GNU ld is more common than GNU gold, so we can just require 'is_binutils_lto_supported' to additionally support GNU ld. Reviewed By: myhsu Differential Revision: https://reviews.llvm.org/D84133
2020-07-23 01:15:51 +08:00
// REQUIRES: binutils_lto
[profile] Move __llvm_profile_raw_version into a separate file Similar to the reason behind moving __llvm_profile_filename into a separate file[1]. When users try to use Full LTO with BFD linker to generate IR level PGO profile, the __llvm_profile_raw_version variable, which is used for marking instrumentation level, generated by frontend would somehow conflict with the weak symbol provided by profiling runtime. In most of the cases, BFD linkers will pick profiling runtime's weak symbol as the real definition and thus generate the incorrect instrumentation level metadata in the final executables. Moving __llvm_profile_raw_version into a separate file would make linkers not seeing the weak symbol in the archive unless the frontend doesn't generate one. [1] https://reviews.llvm.org/D34797 Differential Revision: https://reviews.llvm.org/D83967
2020-07-11 00:40:09 +08:00
[profile][test] Delete profraw directory so that tests are immune to format version upgrade
2021-06-19 07:44:03 +08:00
// RUN: rm -rf %t.profraw
// RUN: %clang_pgogen=%t.profraw/ -fuse-ld=bfd -flto %s -o %t
[profile] Move __llvm_profile_raw_version into a separate file Similar to the reason behind moving __llvm_profile_filename into a separate file[1]. When users try to use Full LTO with BFD linker to generate IR level PGO profile, the __llvm_profile_raw_version variable, which is used for marking instrumentation level, generated by frontend would somehow conflict with the weak symbol provided by profiling runtime. In most of the cases, BFD linkers will pick profiling runtime's weak symbol as the real definition and thus generate the incorrect instrumentation level metadata in the final executables. Moving __llvm_profile_raw_version into a separate file would make linkers not seeing the weak symbol in the archive unless the frontend doesn't generate one. [1] https://reviews.llvm.org/D34797 Differential Revision: https://reviews.llvm.org/D83967
2020-07-11 00:40:09 +08:00
// RUN: %run %t
// RUN: llvm-profdata merge %t.profraw -o %t.profdata
// RUN: llvm-profdata show %t.profdata | FileCheck %s
[profile][test] Add -fuse-ld=bfd to make instrprof-lto-pgogen.c robust Otherwise if 'ld' is an older system LLD (FreeBSD; or if someone adds 'ld' to point to an LLD from a different installation) which does not support the current ModuleSummaryIndex::BitCodeSummaryVersion, the test will fail. Add lit feature 'binutils_lto'. GNU ld is more common than GNU gold, so we can just require 'is_binutils_lto_supported' to additionally support GNU ld. Reviewed By: myhsu Differential Revision: https://reviews.llvm.org/D84133
2020-07-23 01:15:51 +08:00
/// Test that we work around https://sourceware.org/bugzilla/show_bug.cgi?id=26262
/// (as of GNU ld 2.35) which happens when trying to generate IR profile with
/// BFD linker + LLVMgold.so
[profile] Move __llvm_profile_raw_version into a separate file Similar to the reason behind moving __llvm_profile_filename into a separate file[1]. When users try to use Full LTO with BFD linker to generate IR level PGO profile, the __llvm_profile_raw_version variable, which is used for marking instrumentation level, generated by frontend would somehow conflict with the weak symbol provided by profiling runtime. In most of the cases, BFD linkers will pick profiling runtime's weak symbol as the real definition and thus generate the incorrect instrumentation level metadata in the final executables. Moving __llvm_profile_raw_version into a separate file would make linkers not seeing the weak symbol in the archive unless the frontend doesn't generate one. [1] https://reviews.llvm.org/D34797 Differential Revision: https://reviews.llvm.org/D83967
2020-07-11 00:40:09 +08:00
// CHECK: Instrumentation level: IR
int main() { return 0; }