Skip to content

Releases: intel/llvm

DPC++ daily 2022-09-11

11 Sep 16:19
c7289d0

Choose a tag to compare

Pre-release
sycl-nightly/20220911

[SYCL] Pass /Zc:__cplusplus in -fsycl-host-compiler-options in some t…

DPC++ daily 2022-09-10

10 Sep 16:21
c7289d0

Choose a tag to compare

Pre-release
sycl-nightly/20220910

[SYCL] Pass /Zc:__cplusplus in -fsycl-host-compiler-options in some t…

DPC++ daily 2022-09-09

09 Sep 16:20
b81f9df

Choose a tag to compare

Pre-release
[SYCL][NFC] Add SYCLPropagateAspectsUsage pass (#6670)

Added a pass which is a part of optional kernel features design: it uses
information provided by FE & Headers about aspects used in device code
to propagate it through the call graph to mark all kernels and functions
with list of aspects they use.

Co-authored-by: Maksim Sabianin <[email protected]>

DPC++ daily 2022-09-08

08 Sep 16:22
2086035

Choose a tag to compare

Pre-release
[SYCL][Windows] Enable building lld by default on Windows (#6701)

The Windows-Clang CMake module uses `lld-link` by default, so
having lld built on windows is helpful for people wanting to build SYCL
applications using CMake.

Related to: https://github.com/intel/llvm/issues/6026

DPC++ daily 2022-09-07

07 Sep 16:22
33dff95

Choose a tag to compare

Pre-release
[CI][NFC] Rename workflow job (#6572)

Just pure renaming of "resolve test matrix" to "generate test matrix"
Follow up on a comment made at https://github.com/intel/llvm/pull/6528

DPC++ daily 2022-09-06

06 Sep 16:21
4d69c29

Choose a tag to compare

Pre-release
[SYCL][CUDA] Fix get_native interop for device (#6649)

This patch fixes: https://github.com/intel/llvm/issues/6635

In https://github.com/intel/llvm/pull/6483, the implementation of `get_native` for device for the CUDA plugin was mistakenly moved to the experimental interface header, and so it was no longer available for the regular interface, causing build issues.

For the CUDA plugin there is currently two interfaces for the CUDA interop, the "legacy" one which is used by projects such as oneMKL and oneDNN, and the "experimental" one, defined in the `sycl/ext/oneapi/experimental/backend/cuda.hpp` header  which implements the interop as described in the CUDA backend specification proposed here: https://github.com/KhronosGroup/SYCL-Docs/pull/197

DPC++ daily 2022-09-03

03 Sep 16:21
22e3fc5

Choose a tag to compare

Pre-release
[SYCL] Fix template argument propagation in AccessorSubscript (#6669)

Fixes an issue where partial subscripts would fail to compile due to template errors.

Signed-off-by: Larsen, Steffen <[email protected]>

DPC++ daily 2022-09-02

02 Sep 16:21
7b5d4f1

Choose a tag to compare

Pre-release
sycl-nightly/20220902

[SYCL][Doc] Fix doxygen generation: add SYCL_INLINE_VER_NAMESPACE to …

DPC++ daily 2022-09-01

01 Sep 16:21
346a6c5

Choose a tag to compare

Pre-release
[SYCL] Fix depends_on handling with pi commands (#5901)

Fixes two related issues:
1) if pi task is blocked by host task or host accessor it can not be enqueued and piEvent is not present in its event_impl. When we schedule new pi task with explicit (depends_on) dependency on the first one - its is absent in MDeps since we have no usual memory dependencies and present in MPreparedDepsEvents. MPreparedDepsEvents is used in enqueueImp for obtaining piEvents. Any events from MPreparedDepsEvents w/o pi events will be just skipped.
AddDep always call processDepEvent which distributes events to MPreparedDepsEvents (pi event expected) and MPreparedHostDepsEvents (no pi event) so replacement of MDeps in enqueueCommand should be valid.
2) if we have kernel w/o usual memory dependencies (MDeps & MUsers are empty) blocked kernel will be just "cleanup" and its execution will be skipped.

Signed-off-by: Tikhomirova, Kseniya <[email protected]>

DPC++ daily 2022-08-31

31 Aug 16:19
1d95f2e

Choose a tag to compare

Pre-release
[Driver][SYCL] Add support for -fsycl-force-target (#6653)

Introduce -fsycl-force-target=arg support.  This is used along with -fsycl
to allow the user to override the target used to unbundle device objects
from fat objects and archives.

For example, object.o is built from -fsycl-targets=spir64.  The user wants
to build with -fsycl-targets=spir64_gen and object.o.  Use of
-fsycl-force-target=spir64 allows for this to be accomplished.

Additional notes:
  - Only valid when used with a single triple from -fsycl-targets
  - Applies to all unbundled archives and objects