Skip to content

[SYCL] Don't zero-initialize MImageObj in 1.2.1 image #12012

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.

Sign up for GitHub

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

Merged
steffenlarsen merged 1 commit into from
Nov 30, 2023
Merged

[SYCL] Don't zero-initialize MImageObj in 1.2.1 image #12012

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion sycl/include/sycl/accessor.hpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -924,7 +924,7 @@ class image_accessor

#ifdef __SYCL_DEVICE_ONLY__
// Default constructor for objects later initialized with __init member.
image_accessor() : MImageObj() {}
image_accessor() {}
Copy link
Contributor

@MrSidims MrSidims Nov 30, 2023

Choose a reason for hiding this comment

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

tbh can be even removed/defaulted in this case

#endif

// Available only when: accessTarget == access::target::host_image
Expand Down