Skip to content

Task list for Vulkan 1.2 release #1162

Closed

Description

@TomOlson

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/

Activity

  1. hakzsam commented on Jan 15, 2020

    @hakzsam
  2. gfxstrand commented on Jan 15, 2020

    @gfxstrand
    Contributor

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

  3. gfxstrand commented on Jan 15, 2020

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

  4. dneto0 commented on Jan 15, 2020

    @dneto0

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

  5. gnl21 commented on Jan 15, 2020

    @gnl21
    Contributor

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

  6. oddhack commented on Jan 15, 2020

    @oddhack
    Contributor

    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.

  7. johnkslang commented on Jan 15, 2020

    @johnkslang

    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.

  8. johnkslang commented on Jan 15, 2020

    @johnkslang

    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.

  9. gfxstrand commented on Jan 15, 2020

    @gfxstrand
    Contributor

    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.

  10. oddhack commented on Jan 15, 2020

    @oddhack
    Contributor

    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.

  11. johnkslang commented on Jan 15, 2020

    @johnkslang

    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.

  12. dneto0 commented on Jan 15, 2020

    @dneto0

    Shaderc support in google/shaderc#958

  13. krOoze commented on Jan 15, 2020

    @krOoze
    Contributor

    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.

  14. TomOlson commented on Jan 15, 2020

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

  15. dneto0 commented on Jan 15, 2020

    @dneto0

    Shaderc support has been merged into its master.

    @TomOlson: please check the boxes for Shaderc

  16. mikew-lunarg commented on Jan 20, 2020

    @mikew-lunarg
  17. TomOlson commented on Jan 21, 2020

    @TomOlson
    Author

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

  18. mikew-lunarg commented on Jan 29, 2020

    @mikew-lunarg

    SDK released 2020-01-28

    https://vulkan.lunarg.com/

  19. oddhack commented on Dec 15, 2020

    @oddhack
    Contributor

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

  20. chirejaszy commented on May 28, 2021

    @chirejaszy

    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"

  21. marty-johnson59 commented on Jan 25, 2022

    @marty-johnson59
    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions