Releases: intel/llvm
Releases · intel/llvm
DPC++ daily 2022-11-15
sycl-nightly/20221115 [SYCL][PI][L0] Uplift L0 Loader from 1.4.1 to 1.8.8 (#7381)
DPC++ daily 2022-11-14
[LIBCLC] Extend __CLC_NVVM_ATOMIC with generic AS (#7221) The diffs don't show it very well, but this patch extends `__CLC_NVVM_ATOMIC` macro to generate one more overload, targetting a generic address space, while at it, it also fixes a mangled name used in the implementation of `__CLC_NVVM_ATOMIC_IMPL_SUBSTITUTION`.
DPC++ daily 2022-11-11
sycl-nightly/20221111 [InstCombine] PR58901 - fix bug with swapping GEP of different types …
DPC++ daily 2022-11-10
sycl-nightly/20221110 [SYCL][Docs] Move sycl_ext_oneapi_kernel_properties to experimental (…
DPC++ daily 2022-11-09
[SYCL][LIT] Fix narrowing type conversion for marray in test (#7298) Signed-off-by: Tikhomirova, Kseniya <kseniya.tikhomirova@intel.com>
DPC++ daily 2022-11-08
[SYCL] Rename DoubleGRF to LargeGRF (#7284) This change renames double GRF to large GRF both for users and internally in the compiler. We're doing this because we got direct feedback from customer facing engineers that we should use the large GRF terminology, and it also makes the naming consistent with other compiler work we are doing. For the user, ``` set_kernel_properties(kernel_properties::use_double_grf); ``` still works, it will just throw a deprecated warning and will be removed in a future release. The new way is ``` set_kernel_properties(kernel_properties::use_large_grf); ``` There should be no ABI break because we still check the previous image property name in the program manager, so applications built with an old compiler work using the runtime from a new compiler. I confirmed this with manual testing. I will update the system test here to test the new flag as well: https://github.com/intel/llvm-test-suite/blob/intel/SYCL/DeviceCodeSplit/double-grf.cpp Signed-off-by: Sarnie, Nick <nick.sarnie@intel.com>
DPC++ daily 2022-11-07
[SYCL][HIP] Add interop header and devcie specialization (#7145) Fixes https://github.com/intel/llvm/issues/6635 for HIP. Note that it does mean the HIP extension header must be included in user applications in order to get the correct specialization, as is done in the test: ```cpp #include <sycl/ext/oneapi/backend/hip.hpp> ```
DPC++ daily 2022-11-06
[NFC][SYCL] Range reduction refactoring (#7180) To make it look like delegating to NDRange version. I expect some future change completely unify the paths, but this looks like a self-contained atomic improvement.
DPC++ daily 2022-11-05
[SYCL] Enable aspect usage propagation pass and add diagnostics (#6982) This commit adds a warning diagnostic for when there is a mismatch between aspect usage propagated to a function and the function's `device_has` attribute. Additionally, notes accompany the warning to give the user a trace through to where the aspects originate. Since the aspects are propagated in an LLVM pass, the warning is issued from there, which means no source information is available by default. To alleviate this, Clang CodeGen will now add srcloc metadata with an encoded version of the source location to allow the backend to correctly report the location for the various new diagnostics. Additionally, this commit also adds the SYCLPropagateAspectsUsage pass to the passes run for SYCL device code. Signed-off-by: Larsen, Steffen <steffen.larsen@intel.com> Co-authored-by: Sabianin, Maksim <maksim.sabianin@intel.com>
DPC++ daily 2022-11-04
[SYCL][LIT] Remove sycl tests from check-all in Debug mode (#7262) They are extremely slow for Debug compiler and sporadically timeout. It would be still possible to run these through check-sycl target. This is NFC for Github Actions CI since we don't use check-all and call all targets separately.