Brandon Yates

Hey @jjfumero Is there still an open question about spec versioning here, or can this be closed?

zeLoaderInit is not really intended to be an externally visible symbol. It's called from within the loader and isn't currently intended to be called from an external application. There was...

We don't validate this with clang-cl on windows. What cmake commands/options are you using? It looks like cmake is detecting clang-cl as MSVC

@malikm I have a fix that may resolve the windows issue you described. Currently the loader is loading all drivers at startup. My fix moves the driver load into the...

Hi, `ZE_RESULT_ERROR_DEPENDENCY_UNAVAILABLE` is not returned from level zero loader. This is coming from compute-runtime. Can you please move your question to compute-runtime repo?

No, I don't think there is a spec changelog available. This would be nice to have, I'll put in a request for it. Spec 1.3.7 contains a couple typo fixes...

The specs are published here: https://spec.oneapi.com/level-zero/latest/sysman/api.html There's not a public repo for the spec. We are working on correcting it internally. I'll keep you updated.

https://spec.oneapi.com/level-zero/latest/core/api.html#zekernelgetsourceattributes It looks like the implementation of this API in compute-runtime is not compliant with the specification. 1. The memory for the string buffer should be owned by the driver...

The install location of the headers isn't defined in the level zero spec. That's an implementation detail of the loader package. I think it's really up the the application developer...

We don't have an exact equivalent of `clEnqueue{Read/Write}Buffer` , but there are a few different ways to get the behavior you are looking for. Have you tried immediate command lists...