diff options
author | Joseph Huber <huberjn@outlook.com> | 2025-01-27 10:35:27 -0600 |
---|---|---|
committer | GitHub <noreply@github.com> | 2025-01-27 10:35:27 -0600 |
commit | 6ff86f2c0a5b58b07921ee895f0d16d8cd3d4015 (patch) | |
tree | 8fb9fbae66c302370d93736e581badf2de7ea613 /libcxx/src/algorithm.cpp | |
parent | 81d18ad86419fc612c7071e888d11aa923eaeb8a (diff) | |
download | llvm-6ff86f2c0a5b58b07921ee895f0d16d8cd3d4015.zip llvm-6ff86f2c0a5b58b07921ee895f0d16d8cd3d4015.tar.gz llvm-6ff86f2c0a5b58b07921ee895f0d16d8cd3d4015.tar.bz2 |
[AMDGPU] Use the AMDGPUToolChain when targeting C/C++ directly (#99687)
Summary:
The `getToolChain` pass uses the triple to determine which toolchain to
create. Currently the `amdgcn-amd-amdhsa` triple maps to the
`ROCmToolChain` which uses things expected to be provided by `ROCm`.
This is neded for OpenCL, but directly targeting C++ does not want this
since it's primarily being used for creating GPU runtime code. As far as
I know I'm the only user of this, so this shouldn't change anything.
Unfortunately, there's no good logic for detercting this, so I simply
checked ahead of time if the input is either `foo.cl` or `-x cl foo.c`
to choose between the two. This allows us to use the AMDGPU target
normally, as otherwise it will error without passing `-nogpulib`.
Diffstat (limited to 'libcxx/src/algorithm.cpp')
0 files changed, 0 insertions, 0 deletions