We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug In sycl/source/detail/sycl_mem_obj_t.hpp, there is a memcpy call that fails during build as follows: [2023-07-14T04:10:16.104Z] /netbatch/donb1156623_00/runDir/jenkins-dir/workspace/SYCL_CI/intel/Build_PR_RHEL/llvm.src/sycl/source/detail/sycl_mem_obj_t.hpp:195:18: error: argument 2 null where non-null expected [-Werror=nonnull] This failure is seen in #10379 which has only test update. Full log: http://icl-jenkins2.sc.intel.com:8080/blue/rest/organizations/jenkins/pipelines/SYCL_CI/pipelines/intel/pipelines/Build_PR_RHEL/runs/6462/log/?start=0
[2023-07-14T04:10:16.104Z] /netbatch/donb1156623_00/runDir/jenkins-dir/workspace/SYCL_CI/intel/Build_PR_RHEL/llvm.src/sycl/source/detail/sycl_mem_obj_t.hpp:195:18: error: argument 2 null where non-null expected [-Werror=nonnull]
To Reproduce Please look at full log provided above.
Additional context #10334 seems to be a possible reason.
Thanks
The text was updated successfully, but these errors were encountered:
Fixed in #10426.
Sorry, something went wrong.
No branches or pull requests
Describe the bug
In sycl/source/detail/sycl_mem_obj_t.hpp, there is a memcpy call that fails during build as follows:
[2023-07-14T04:10:16.104Z] /netbatch/donb1156623_00/runDir/jenkins-dir/workspace/SYCL_CI/intel/Build_PR_RHEL/llvm.src/sycl/source/detail/sycl_mem_obj_t.hpp:195:18: error: argument 2 null where non-null expected [-Werror=nonnull]
This failure is seen in #10379 which has only test update.
Full log: http://icl-jenkins2.sc.intel.com:8080/blue/rest/organizations/jenkins/pipelines/SYCL_CI/pipelines/intel/pipelines/Build_PR_RHEL/runs/6462/log/?start=0
To Reproduce
Please look at full log provided above.
Additional context
#10334 seems to be a possible reason.
Thanks
The text was updated successfully, but these errors were encountered: