-
Inspired by recent events (#765), (#766), (#709), I thought it would be a good idea to kick off a discussion related to upstream compatibilities for hipSYCL.
# Main Point
HipSYCL is currently buil…
-
Hey! Cool work, bringing GPU compute to Go at this level. I found this through your RWA work.
I have AMD cards that support [HIP](https://github.com/RadeonOpenCompute/ROCm), which is ~ a subset of …
ghost updated
7 years ago
-
```
sycl::buffer buf_target(target, coeff_count*decomp_mod_count);
sycl::buffer buf_lsp_0(local_small_poly_0.get(), coeff_count);
sycl::buffer buf_lsp_1(local_small_poly_1.get(), coeff_count); …
-
It looks like the current proposal does not have the usual `a[j][j][k]` syntax.
Since it cannot be an omission :-) , what are the reasons for this absence?
It is available in `std::valarray`, https:…
-
I'm on the current `sycl/unified/next` branch and using Vitis 2020.2 with a `xilinx_u200_xdma_201830_2` target. Compiling the `single_task_vector_add` test case works fine but it fails once `vpl` is c…
-
I've installed hipSYCL stable using the spack package.
Setting following options before compiling:
```
source /home/marcel/Programs/spack/share/spack/setup-env.sh
spack load hipsycl@master
spa…
-
I usually use the default_device selector and with the proper export SYCL_DEVICE_FILTER to execute on device
and add a SYCL_DEVICE_FILTER=host when debugging on cpu.
but now I receive this message.
…
-
In an attempt to work around #107 I tried to compile the toolchain with Ubuntu 20.04's default clang:
```
> clang --version
clang version 10.0.0-4ubuntu1
Target: x86_64-pc-linux-gnu
Thread mod…
-
This is a non-exhaustive list of some larger problems relating to XIlinx FPGA compilation and runtime execution (some with more information than others) that need some thought long term:
----------…
-
https://github.com/intel/llvm/issues/6055 raised the issue that some implementations may allow `make_device` to return a duplicate sycl::device if there is already a `sycl::device` owning the specifie…