[FEA]: llvm / clang 17 CI coverage

[jgehrcke]

Is this a duplicate?

• I confirmed there appear to be no duplicate issues for this request and that I agree to the Code of Conduct

Area

libcu++

Is your feature request related to a problem? Please describe.

Hello! We see that in CI you are covering the binaries from the LLVM 16.x releases, but there is no coverage yet for the 17.x releases:

cccl/ci/matrix.yaml

Line 34 in c494fe9

llvm-newest: &llvm-newest { name: 'llvm', version: '16', exe: 'clang++' }

That's something that is very interesting for us.

Anecdote: we are debugging a clang-tidy error which is actually a compilation error: clang is tripped up by code in libcudacxx/cuda/std/detail/libcxx/include and for our debugging it was interesting to see where you are in terms of supporting clang 17.

Describe the solution you'd like

cover clang 17 in your CI

Describe alternatives you've considered

n/a

Additional context

No response

[miscco]

Did they perchance add another builtin that is named like a function?

[miscco]

I have opened a PR to add clang-17 to our CI matrix.

[jgehrcke]

I have opened a PR to add clang-17 to our CI matrix.

Thank you! That is a super fast turnaround. I trust that this will be useful, but I am also slightly sorry because in the meantime we have understood the root cause of our troubles. I have summarized that here:
rapidsai/rmm#1307 (comment)

You have nicely patched the problem we were seeing a long while ago (for clang 16 support), but rapids memory manager 23.12 vendors an old version of libcudacxx! :) sorry for the noise 🔊