level-zero icon indicating copy to clipboard operation
level-zero copied to clipboard
verified publisher icon oneapi-src

Image API intentionally not backwards compatible?

Open Ruyk opened this issue 5 years ago • 2 comments

From https://spec.oneapi.com/versions/0.7/oneL0/core/PROG.html#images:

This methodology allows for device-specific encoding of image contents (e.g., tile swizzle patterns, lossless compression, etc.) and avoids exposing these details in the API in a backwards compatible fashion.

Is that wording intentional? I would assume backwards compatibility for the Image API is a desired quality , not something to avoid...

Ruyk avatar May 21 '20 09:05 Ruyk

I think we forgot another negation in there. Thanks for pointing this out; we will fix it to clearly say we intend to maintain backward compatibility.

gatorfax avatar May 23 '20 23:05 gatorfax

Unfortunately, this didn't make it into the most recent 0.95 spec. But this entire paragraph will be rewritten in the next release.

The intent was to say: by not allowing direct Host access to image memory, the API did not need to add complex, backwards compatible APIs for vendor-specific layouts, swizzle patterns, etc.

gatorfax avatar Jun 02 '20 00:06 gatorfax