Steffen Larsen

/verify with https://github.com/intel/llvm-test-suite/pull/1002

Failure during build: ``` [2870/2938] Generating ../../lib/libsycl-fallback-complex.o FAILED: lib/libsycl-fallback-complex.o cd .../LLVM_Test_Suite/llvm.obj/tools/libdevice && .../LLVM_Test_Suite/llvm.obj/bin/clang-15 -fsycl -c -Wno-sycl-strict -Wno-undefined-internal -sycl-std=2020 -fno-sycl-libspirv -fno-bundle-offload-arch -fsycl-targets=spir64_x86_64-unknown-unknown,spir64_gen-unknown-unknown,spir64_fpga-unknown-unknown,spir64-unknown-unknown,nvptx64-nvidia-cuda .../LLVM_Test_Suite/llvm.src/libdevice/fallback-complex.cpp -o .../LLVM_Test_Suite/llvm.obj/lib/libsycl-fallback-complex.o clang-15: error: cannot find libdevice for...

@jinge90 & @smanna12 - Friendly ping.

This is a reopening of https://github.com/intel/llvm/pull/4889 as we are now able to break ABI.

For the sake of reviving this discussion, I agree with @AaronBallman that the only way to be fully out of the woods is to use reserved identifiers in our headers,...

During internal discussion the following concerns were brought up: 1. Do internal macros also need to follow the reserved naming requirements? If yes, how can we be sure it does...

https://github.com/intel/llvm/pull/6493 - Small fix for a handful of known cases of commonly defined macro names. This is not intended as a resolution to this issue, but as a temporary work-around...

Patch https://github.com/intel/llvm/pull/6815 by @AlexeySachkov currently uses reserved identifiers in a detail header implementation. This may change to make it more consistent with the rest of the subproject, but mentioning it...

Failing test is unrelated and was disabled separately.

XPTI makes assumptions about the number of arguments in reduction kernels. Since this patch adds the `PerGroup` as an implicit argument these assumptions fail. https://github.com/intel/llvm-test-suite/pull/1040 updates these values. An alternative...