Skip to content
New issue

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

[SYCL] removing std::memcpy from sycl headers #11436

Merged
merged 3 commits into from
Oct 16, 2023

Conversation

cperkinsintel
Copy link
Contributor

@cperkinsintel cperkinsintel commented Oct 4, 2023

removing std::memcpy from sycl headers, continuation of work originally done in #1117.

@cperkinsintel cperkinsintel temporarily deployed to WindowsCILock October 4, 2023 22:27 — with GitHub Actions Inactive
@cperkinsintel cperkinsintel temporarily deployed to WindowsCILock October 4, 2023 23:32 — with GitHub Actions Inactive
@cperkinsintel cperkinsintel temporarily deployed to WindowsCILock October 13, 2023 00:06 — with GitHub Actions Inactive
@cperkinsintel cperkinsintel temporarily deployed to WindowsCILock October 13, 2023 00:32 — with GitHub Actions Inactive
@cperkinsintel cperkinsintel marked this pull request as ready for review October 13, 2023 01:39
Copy link
Contributor

@steffenlarsen steffenlarsen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

Copy link
Contributor

@dkhaldi dkhaldi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@joeatodd joeatodd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As @YuriPlyakhin correctly points out, the use of std::memcpy in sycl/include/syclcompat/memory.hpp is host code copying host memory, so I think that should remain as std::memcpy.

@cperkinsintel cperkinsintel temporarily deployed to WindowsCILock October 16, 2023 15:54 — with GitHub Actions Inactive
@cperkinsintel cperkinsintel temporarily deployed to WindowsCILock October 16, 2023 16:19 — with GitHub Actions Inactive
@againull againull merged commit 819a94a into intel:sycl Oct 16, 2023
@againull
Copy link
Contributor

@cperkinsintel ,
It seems that there is a CI post-commit failure after your commit:


Failed Tests (1):
SYCL :: Matrix/XMX8/joint_matrix_all_sizes.cpp

Could you please take a look?

@kbenzie
Copy link
Contributor

kbenzie commented Oct 17, 2023

I think this might be causing the DeviceLib/built-ins/ext_native_math.cpp test to fail in the CUDA adapter: https://github.com/intel/llvm/actions/runs/6548481823/job/17783308369

aelovikov-intel added a commit that referenced this pull request Dec 23, 2024
See #1117 and
#11436 for the context.

In this mode, `std::memcpy` cannot be used in device code, but its usage
occasionally leaks into our code base. I think testing the configuration
in CI is the easiest way to prevent that with at least some confidence.
Another option would be to modify FE to report any usage of
`std::memcpy` in device code only, but I don't know if that's even
possible.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants