Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
A
angle
  • Project
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Chen Yisong
  • angle
  • Repository

Switch branch/tag
  • angle
  • src
  • common
  • vulkan
  • vulkan_icd.cpp
Find file
BlameHistoryPermalink
  • Alexis Hetu's avatar
    Fix using VK_EXT_provoking_vertex with VVL · c02d5f12
    Alexis Hetu authored Apr 27, 2021
    Vulkan Validation Layers (VVL) automatically rejects and
    removes any unknown pNext pointer in an pNext chain
    submitted to the driver. For this purpose, a mechanism was
    introduced by VVL in order to allow ANGLE to allow some of
    our custom pNext entries to go through VVL without being
    removed. This had been used for only 1 of the 3 entries in
    the VK_EXT_provoking_vertex extension, causing it to be
    properly exposed, but impossible to use. This CL corrects
    this by adding the missing entries.
    
    Bug: angleproject:5902
    Change-Id: If6478b3aa776513b92420736fa1216b014320b02
    Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2854815Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org>
    Reviewed-by: 's avatarCody Northrop <cnorthrop@google.com>
    Commit-Queue: Alexis Hétu <sugoi@chromium.org>
    c02d5f12
vulkan_icd.cpp 9.15 KB
EditWeb IDE
×

Replace vulkan_icd.cpp

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.