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

[Exp][Bindless Images] Add BI revision 4 functionality #655

Merged

Conversation

przemektmalon
Copy link
Contributor

  • Added bindless images revision 4 API changes
  • Fixed some errors from revision 3

- Added bindless images revision 4 API changes
- Fixed some errors from revision 3

Co-authored-by: Isaac Ault <isaac.ault@codeplay.com>
Co-authored-by: Przemek Malon <przemek.malon@codeplay.com>
@veselypeta veselypeta merged commit 78aebac into oneapi-src:main Jun 27, 2023
18 checks passed
BINDLESS_IMAGES_3D_USM_SUPPORT_EXP = 0x2003 ## [::ur_bool_t] returns true if the device supports the creation of 3D
## bindless images backed by USM
IMAGE_PITCH_ALIGN_EXP = 0x2004 ## [uint32_t] returns the required alignment of the pitch between two
IMAGE_PITCH_ALIGN_EXP = 0x2003 ## [uint32_t] returns the required alignment of the pitch between two
Copy link

Choose a reason for hiding this comment

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

Are we okay with these numbers changing because the feature is experimental?

In general can we catch ABI changes like this automatically?

Copy link

Choose a reason for hiding this comment

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

Obviously this PR is fully of ABI changes, with all the function signature changes. So the enum change is no different to those. Just in general it's easier to miss.

Copy link
Contributor

Choose a reason for hiding this comment

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

Experimental features are free to break their own ABI/API - we have some checks to ensure that the core API is unaffected.

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.

4 participants