Skip to content
This repository was archived by the owner on Mar 28, 2023. It is now read-only.

[SYCL] Rename deprecated access::target::global_buffer #647

Merged
merged 3 commits into from Jan 17, 2022
Merged

[SYCL] Rename deprecated access::target::global_buffer #647

merged 3 commits into from Jan 17, 2022

Conversation

ghost
Copy link

@ghost ghost commented Dec 21, 2021

The sycl::access::target::global_buffer enumeration is deprecated in SYCL 2020,
the target::device one should be used instead.

Signed-off-by: Pavel Samolysov [email protected]

Pavel Samolysov added 3 commits December 21, 2021 11:41
The sycl::access::target::global_buffer enumeration is deprecated in SYCL 2020,
the target::device one should be used instead.

Signed-off-by: Pavel Samolysov <[email protected]>
Signed-off-by: Pavel Samolysov <[email protected]>
Signed-off-by: Pavel Samolysov <[email protected]>
@ghost ghost marked this pull request as ready for review December 22, 2021 06:48
Copy link

@AlexeySachkov AlexeySachkov left a comment

Choose a reason for hiding this comment

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

Should we leave at least one test which checks the old variant?

cl::sycl::access::target::global_buffer>;
cl::sycl::access::target::device>;

Choose a reason for hiding this comment

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

Moving from SYCL 1.2.1 to SYCL 2020 should change three things about this line:

  1. The cl::sycl:: namespace should be sycl:: instead, since cl:: comes in only via <CL/sycl.hpp>
  2. sycl::access::target should be sycl::target because the former is deprecated (see here)
  3. global_buffer should be device (as changed in your patch)

Is there a reason to only make the global_buffer => device change here?

Copy link
Author

Choose a reason for hiding this comment

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

@Pennycook Yes, the reason is just to change global_buffer => device here, moving from SYCL 1.2.1 to SYCL 2020 is a more global initiative.

Choose a reason for hiding this comment

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

Ok. I still think moving these things to the right namespace now would save time, but I won't argue.

Copy link
Author

Choose a reason for hiding this comment

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

I see, there is a mix of the cl::sycl:: and just sycl:: namespaces in this file, for example it uses cl::sycl:: for access::target or property, but sycl:: for ::access::mode or buffer, or id. I'm going to fix the namespace mismatch in another PR.

@vladimirlaz vladimirlaz merged commit 2058d12 into intel:intel Jan 17, 2022
myler pushed a commit to myler/llvm-test-suite that referenced this pull request Apr 12, 2022
The sycl::access::target::global_buffer enumeration is deprecated in SYCL 2020,
the target::device one should be used instead.

Signed-off-by: Pavel Samolysov <[email protected]>
myler pushed a commit to myler/llvm-test-suite that referenced this pull request Apr 12, 2022
The sycl::access::target::global_buffer enumeration is deprecated in SYCL 2020,
the target::device one should be used instead.

Signed-off-by: Pavel Samolysov <[email protected]>
myler pushed a commit to myler/llvm-test-suite that referenced this pull request Jun 17, 2022
The sycl::access::target::global_buffer enumeration is deprecated in SYCL 2020,
the target::device one should be used instead.

Signed-off-by: Pavel Samolysov <[email protected]>
aelovikov-intel pushed a commit to aelovikov-intel/llvm that referenced this pull request Mar 27, 2023
…st-suite#647)

The sycl::access::target::global_buffer enumeration is deprecated in SYCL 2020,
the target::device one should be used instead.

Signed-off-by: Pavel Samolysov <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants