aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorJoseph Huber <huberjn@outlook.com>2025-03-28 07:35:16 -0500
committerGitHub <noreply@github.com>2025-03-28 07:35:16 -0500
commit772173f54868eef6e1a4d40ab93b0ee6c04b1aca (patch)
tree076be76b230271def1a71dab9e9cff02ab837070 /clang/lib/Frontend/CompilerInvocation.cpp
parentc4bc1b1d8177961c50c7a197bfb97b5226e749ff (diff)
downloadllvm-772173f54868eef6e1a4d40ab93b0ee6c04b1aca.zip
llvm-772173f54868eef6e1a4d40ab93b0ee6c04b1aca.tar.gz
llvm-772173f54868eef6e1a4d40ab93b0ee6c04b1aca.tar.bz2
[Clang][AMDGPU] Remove special handling for COV4 libraries (#132870)
Summary: When we were first porting to COV5, this lead to some ABI issues due to a change in how we looked up the work group size. Bitcode libraries relied on the builtins to emit code, but this was changed between versions. This prevented the bitcode libraries, like OpenMP or libc, from being used for both COV4 and COV5. The solution was to have this 'none' functionality which effectively emitted code that branched off of a global to resolve to either version. This isn't a great solution because it forced every TU to have this variable in it. The patch in https://github.com/llvm/llvm-project/pull/131033 removed support for COV4 from OpenMP, which was the only consumer of this functionality. Other users like HIP and OpenCL did not use this because they linked the ROCm Device Library directly which has its own handling (The name was borrowed from it after all). So, now that we don't need to worry about backward compatibility with COV4, we can remove this special handling. Users can still emit COV4 code, this simply removes the special handling used to make the OpenMP device runtime bitcode version agnostic.
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions