Alexey Sachkov

> Just curious - did you try warnings.cpp actually? Not sure, but I think I tried it sometime ago and there was no need for a separate test. `warnings.cpp` is...

> > I'd also suggest to update our [code](https://github.com/intel/llvm/blob/sycl/sycl/source/detail/device_impl.cpp#L378), so we don't use this deprecated query. > > That's a good point! `warnings.cpp` should be updated to fail unless this...

@cperkinsintel, @intel/llvm-reviewers-runtime, could you please take a look?

> what will happen with ext_oneapi_get_default_context then? Will it be deprecated? Good question. I think that deprecating it is the right way to go, but we need to double-check that...

Hi @jinz2014, From [5.4. Language restrictions for device functions](https://registry.khronos.org/SYCL/specs/sycl-2020/html/sycl-2020.html#sec:language.restrictions.kernels): > The rules for kernels apply to both the kernel function objects themselves and all functions, operators, member functions, constructors and...

> Could the "experimental" API change soon so that "sycl::complex" will not cause compiler errors ? I don't think that we will do that. Whilst I don't see a strict...

> Hey, just wondering: Would this list all possible `-fsycl-targets`? or just the ones supported by the build of the compiler? (For example, if we build the compiler without cuda...

> > For example, if we build the compiler without cuda support it wouldn't list the nvptx64-nvidia-cuda target > > From a user's perspective, this would be bad. It would...

This topic was recently re-evaluated and apparently we (Intel) prefer all security issues reported through a single channel. Therefore, we won't be enabling private vulnerability reporting on GitHub. Our security...

I see `XPASS`es locally and in our internal downstream testing for: ``` sycl/test-e2e/Basic/accessor/accessor.cpp sycl/test-e2e/DeviceArchitecture/device_architecture_comparison_on_device_aot.cpp ``` Both are updated to drop `XFAIL` by #16131