summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTom Stellard <tstellar@redhat.com>2024-04-16 17:21:15 -0700
committerGitHub <noreply@github.com>2024-04-16 17:21:15 -0700
commite6c3289804a67ea0bb6a86fadbe454dd93b8d855 (patch)
tree6406d18a97ae4a051f9c1aafacf7994de2e12923
parent028e425f86ccff44aa521c2e2ac428dbda2c13d4 (diff)
[CMake][Release] Disable PGO (#88465) (#89000)llvmorg-18.1.4
Running the test-release.sh script with PGO enabled causes build errors like: ld.lld: error: Function Import: link error: linking module flags 'ProfileSummary': IDs have conflicting values I believe this a build system bug due to the PGO profile data being generated unconditionally. If you run `ninja check-all` and then `ninja install` like we do in test-release.sh, then the profile data is regenerated during `ninja install` and some of the clang tools which are not test dependencies get build during the ninja install step with different profile data. When these tools link against the LLVM libraries, like libSupport, we end up with these errors. (cherry picked from commit 0d2bb7f017f13ceae793fab7d83d3e67e8d8d8f8)
-rw-r--r--clang/cmake/caches/Release.cmake2
1 files changed, 1 insertions, 1 deletions
diff --git a/clang/cmake/caches/Release.cmake b/clang/cmake/caches/Release.cmake
index 1ca9138b9807..bd1f688d61a7 100644
--- a/clang/cmake/caches/Release.cmake
+++ b/clang/cmake/caches/Release.cmake
@@ -4,7 +4,7 @@
# General Options
set(LLVM_RELEASE_ENABLE_LTO THIN CACHE STRING "")
-set(LLVM_RELEASE_ENABLE_PGO ON CACHE BOOL "")
+set(LLVM_RELEASE_ENABLE_PGO OFF CACHE BOOL "")
set(CMAKE_BUILD_TYPE RELEASE CACHE STRING "")