[all-commits] [llvm/llvm-project] 76af6e: [libc] Manually set the AMDGPU code object version...
Joseph Huber via All-commits
all-commits at lists.llvm.org
Mon Sep 11 11:08:10 PDT 2023
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 76af6e77c0e5d8c444daa3aea07f381c07b17da7
https://github.com/llvm/llvm-project/commit/76af6e77c0e5d8c444daa3aea07f381c07b17da7
Author: Joseph Huber <35342157+jhuber6 at users.noreply.github.com>
Date: 2023-09-11 (Mon, 11 Sep 2023)
Changed paths:
M libc/cmake/modules/LLVMLibCObjectRules.cmake
M libc/cmake/modules/LLVMLibCTestRules.cmake
M libc/cmake/modules/prepare_libc_gpu_build.cmake
M libc/startup/gpu/amdgpu/CMakeLists.txt
M libc/test/IntegrationTest/CMakeLists.txt
Log Message:
-----------
[libc] Manually set the AMDGPU code object version (#65986)
Summary:
There is currently effort to change over the default AMDGPU code object
version https://github.com/llvm/llvm-project/pull/65410. However, this
unfortunately causes problems in the LLVM LibC test suite that leads to
a hang while executing. This is most likely a bug to do with indirect
call optimization, as it can be avoided without optimizations or with
manually preventing inlining in the AMDGPU startup code.
This patch sets the AMDGPU code object version to be four explicitly on
the LibC test suite. This should unblock the efforts to move the default
to 5 without breaking the test suite. This isn't a great solution, but
there is currently some time pressure to get COV5 landed and this seems
to be the easiest solution.
More information about the All-commits
mailing list