You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying to use the DPCT headers in a project and got into this following issue. SYCLomatic built with GCC 13.3.0
/vast/users/abagusetty/compilers/today/llvm/build_hip6.3.0_01-28-2025/install/bin/../include/CL/sycl.hpp:14:2: warning: "CL/sycl.hpp is deprecated, use sycl/sycl.hpp" [-W#warnings]
14 |#warning "CL/sycl.hpp is deprecated, use sycl/sycl.hpp"| ^
In file included from ./dpcpp/kernels.dp.cpp:27:
In file included from /vast/users/abagusetty/compilers/today/SYCLomatic/install-hip6.3.0_01-28-2025/include/dpct/dpct.hpp:52:
/vast/users/abagusetty/compilers/today/SYCLomatic/install-hip6.3.0_01-28-2025/include/dpct/device.hpp:595:21: error: no matching member functionfor call to 'push_back'
595 |last_events.push_back(q->ext_oneapi_get_last_event());
|~~~~~~~~~~~~^~~~~~~~~
/soft/compilers/gcc/13.3.0/x86_64-suse-linux/lib/gcc/x86_64-pc-linux-gnu/13.3.0/../../../../include/c++/13.3.0/bits/stl_vector.h:1281:7: note: candidate functionnot viable: no known conversion from 'std::optional<event>' to 'const value_type' (aka 'const sycl::event') for 1st argument
1281 | push_back(const value_type& __x)
| ^ ~~~~~~~~~~~~~~~~~~~~~
/soft/compilers/gcc/13.3.0/x86_64-suse-linux/lib/gcc/x86_64-pc-linux-gnu/13.3.0/../../../../include/c++/13.3.0/bits/stl_vector.h:1298:7: note: candidate functionnot viable: no known conversion from 'std::optional<event>' to 'value_type' (aka 'sycl::event') for 1st argument
1298 | push_back(value_type&& __x)
| ^ ~~~~~~~~~~~~~~~~
To reproduce
No response
Environment
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
I was trying to use the DPCT headers in a project and got into this following issue. SYCLomatic built with GCC 13.3.0
To reproduce
No response
Environment
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: