-
Notifications
You must be signed in to change notification settings - Fork 880
Implement GL_EXT_bfloat16 #3905
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
Conversation
The spirv-tools support has landed. I've rebased and updated the deps, this is ready for review now. Ping @jeremy-lunarg @arcady-lunarg. |
addExtension(spv::E_SPV_KHR_bfloat16); | ||
addCapability(CapabilityBFloat16TypeKHR); | ||
|
||
#if 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any plan to add the necessary support to the debuginfo spec? Also, have you tested this extension with debuginfo enabled to make sure it at least successfully fails to emit debuginfo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't personally have any plans to do a followon debuginfo extension. It seems like it wasn't made extensible enough to support new types it didn't foresee. I tried running the bfloat16 unit test with debuginfo and it asserts here:
Id Builder::makeDebugFunctionType(Id returnType, const std::vector<Id>& paramTypes)
{
assert(debugId[returnType] != 0);
So, yeah, debuginfo may not work. But I'm not sure what to do about it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I should add - that test did run to completion (in release), generates code, but that code fails validation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the interests of getting this done, I would say it's okay to not deal with debuginfo for now and open a glslang issue for the assertion failure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, I filed #3925 about this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Edit: spirv-tools has landed, this is ready for review.
Spec is at KhronosGroup/GLSL#279