Image API intentionally not backwards compatible?

oneapi-src / level-zero

oneAPI Level Zero Specification Headers and Loader

https://spec.oneapi.com/versions/latest/elements/l0/source/index.html

MIT License

218 stars 96 forks source link

Image API intentionally not backwards compatible? #24

Open Ruyk opened 4 years ago

Ruyk commented 4 years ago

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...

gatorfax commented 4 years ago

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 commented 4 years ago

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.