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

Task list for Vulkan 1.2 release #1162

Closed
10 of 11 tasks
TomOlson opened this issue Jan 15, 2020 · 22 comments
Closed
10 of 11 tasks

Task list for Vulkan 1.2 release #1162

TomOlson opened this issue Jan 15, 2020 · 22 comments

Comments

@TomOlson
Copy link

TomOlson commented Jan 15, 2020

Vulkan 1.2 promotes 23 previously released Vulkan extensions into a new core specification, and adds other minor features to improve integration and ease of use. The complete list of new features can be found in Appendix D of the specification.

Vulkan is an ecosystem-driven API; the Vulkan and SPIR-V Working Groups define the specification, but the tools developers need to use the API come many teams across the Vulkan community. This issue tracks the state of the various documents and software artifacts needed to develop Vulkan 1.2 applications. As each item is made public, the task will be checked off below. When all tasks have been checked off, this issue will be closed and the Vulkan 1.2 release will be complete. Unless otherwise noted, the target release date for all items is on or before January 31, 2020.

The task list for the Vulkan 1.2 release is:

Public installable Vulkan 1.2 drivers are available for download from the following vendors at the supplied URLs:

Source code for Mesa drivers from Intel (for Intel GPUs) and from the Mesa RADV team (for AMD GPUs) can be found at https://gitlab.freedesktop.org/mesa/mesa/

@hakzsam
Copy link

hakzsam commented Jan 15, 2020

@TomOlson RADV MR https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3410

@gfxstrand
Copy link
Contributor

gfxstrand commented Jan 15, 2020

Please, people, when you edit the task list, make sure you refresh your page immediately before hand. Edits are getting lost left and right. Either that or only @TomOlson should edit. We also appear (from what I'm seeing) to also be seeing a failure of the gitlab MR edit draft system where even if you do refresh stuff may get lost when you click "edit". You have to edit then discard then edit again to get a proper refresh. ☹️

@gfxstrand
Copy link
Contributor

@TomOlson RADV MR https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3410

Both RADV and Intel Linux have now been merged into mesa master.

@dneto0
Copy link

dneto0 commented Jan 15, 2020

SPIRV-Tools support: KhronosGroup/SPIRV-Tools#3137

@gnl21
Copy link
Contributor

gnl21 commented Jan 15, 2020

The glslang link looks wrong. The correct link is: KhronosGroup/glslang#2058

@oddhack
Copy link
Contributor

oddhack commented Jan 15, 2020

Please, people, when you edit the task list, make sure you refresh your page immediately before hand. Edits are getting lost left and right. Either that or only @TomOlson should edit. We also appear (from what I'm seeing) to also be seeing a failure of the gitlab MR edit draft system where even if you do refresh stuff may get lost when you click "edit". You have to edit then discard then edit again to get a proper refresh.

Ditto. I keep trying to click the "headers" item as being done and it appears to reflect it, then I come back to the page later and it's back to unchecked. Seems like Github needs better locking around updates.

@johnkslang
Copy link
Member

But, some of this could be browser caching, and the browser submitting older versions as the update, which GitHub can't control.

I re-clicked the headers for you, see how long it sticks.

@johnkslang
Copy link
Member

The glslang link looks wrong. The correct link is: KhronosGroup/glslang#2058

I'm sure I had 2058 to begin with, will carefully try updating again, once bots finish, with the new location.

@gfxstrand
Copy link
Contributor

gfxstrand commented Jan 15, 2020

But, some of this could be browser caching, and the browser submitting older versions as the update, which GitHub can't control.

GitHub could make it so that an edit sends both the new text and what it thinks the old text was and do an atomic_compare_exchange. You'd still have the ABA problem but at least it'd be better. Also, they clearly have the history of all edits so they could send along which edit the current one is based on and reject if it doesn't match. 😄 Even Bugzilla manages to get this right.

@oddhack
Copy link
Contributor

oddhack commented Jan 15, 2020

Also, they clearly have the history of all edits so they could send along which edit the current one is based on and reject if it doesn't match. Even Bugzilla manages to get this right.

If only GH had access to some sort of "revision control" software that would keep track of changes and could tell when conflicts arose... naah, dreaming again.

@johnkslang
Copy link
Member

johnkslang commented Jan 15, 2020

I've updated check-off items for Vulkan headers, glslang, and SPIRV-Tools, as well as the location of the latter two. All seem to be sticking and didn't seem to lose anything.

@dneto0
Copy link

dneto0 commented Jan 15, 2020

Shaderc support in google/shaderc#958

@krOoze
Copy link
Contributor

krOoze commented Jan 15, 2020

But, some of this could be browser caching, and the browser submitting older versions as the update, which GitHub can't control.

It could. Though I think the post editing is mostly meant for moderation, not for collaboration.

PS: there is a Projects feature, which you could try to use for this instead, maybe.

@TomOlson
Copy link
Author

Definitely issues arising between browser caching and how the GH site behaves. But let's take those inside Khronos - not very interesting for people trying to track the Vulkan 1.2 release. Next time we do this, we'll find a different mechanism.

@dneto0
Copy link

dneto0 commented Jan 15, 2020

Shaderc support has been merged into its master.

@TomOlson: please check the boxes for Shaderc

@alegal-arm
Copy link

@mikew-lunarg
Copy link

@TomOlson
Copy link
Author

I have deleted the "GLSL specification" deliverable - turns out there are no updates.

@mikew-lunarg
Copy link

mikew-lunarg commented Jan 29, 2020

SDK released 2020-01-28

https://vulkan.lunarg.com/

@oddhack
Copy link
Contributor

oddhack commented Dec 15, 2020

@TomOlson do you know who owns the DXC support checklist item and/or its status? Unlike the others there's no outward link to that repo, or owner, but it was supposed to be resolved 6 months ago. With that we could close this tracker.

@chirejaszy
Copy link

chirejaszy commented May 28, 2021

executor --connect=127.0.0.1 --port=50016 --binaryname=
com.drawelements.deqp/android.app.NativeActivity
--caselistdir=caselists
--testset=dEQP-GLES2.* --out=BatchResult.qpa
--cmdline="--deqp-crashhandler=enable --deqp-watchdog=enable
--deqp-gl-config-name=rgba8888d24s8"

@marty-johnson59
Copy link
Contributor

Closing as we're clearly done with this now:)

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

No branches or pull requests