layers: Fix extension func/core struct codegen

Fix code generation for extension functions receiving struct parameter
types defined by core Vulkan.  Extensions are processed as separate
features by the code generator, and the type info required for structure
generation was not being shared across features.  The code generator has
been modified to share type info across features so that the validation
code generated for extension functions includes validation for core
structures:
 - Prevent unique objects and parameter validation code generators from
   clearing struct type info data structures at the start of feature
   processing.
 - Remove unused data structures from unique objects code generator.
 - Adds handle unwrapping and parameter validation for elements in the
   vkCmdPushDescriptorSetKHR pDescriptorWrites parameter.
 - Adds handle unwrapping and parameter validation for elements in the
   vkCreateSharedSwapCHainsKHR pCreateInfos parameter.
 - Adds VkAllocationCallback parameter validation to the WSI and
   descriptor update template extensions functions.

Change-Id: I016aa6550681dbf7d6bda834272374ce63ed1940
3 files changed
tree: 6be953b05f6ad27c726d73982a05d9e6f25a1bd9
  1. build-android/
  2. cmake/
  3. common/
  4. external_revisions/
  5. include/
  6. layers/
  7. loader/
  8. scripts/
  9. tests/
  10. windowsRuntimeInstaller/
  11. .appveyor.yml
  12. .clang-format
  13. .gitignore
  14. .travis.yml
  15. BUILD.md
  16. build_windows_targets.bat
  17. CMakeLists.txt
  18. CONTRIBUTING.md
  19. COPYRIGHT.txt
  20. LICENSE.txt
  21. README.md
  22. update_external_sources.bat
  23. update_external_sources.sh
README.md

Vulkan Ecosystem Components

This project provides Khronos official ICD loader and validation layers for Vulkan developers on Windows and Linux.

CI Build Status

PlatformBuild Status
Linux/AndroidBuild Status
WindowsBuild status

Introduction

Vulkan is an Explicit API, enabling direct control over how GPUs actually work. No (or very little) validation or error checking is done inside a Vulkan driver. Applications have full control and responsibility. Any errors in how Vulkan is used often result in a crash. This project provides standard validation layers that can be enabled to ease development by helping developers verify their applications correctly use the Vulkan API.

Vulkan supports multiple GPUs and multiple global contexts (VkInstance). The ICD loader is necessary to support multiple GPUs and the VkInstance level Vulkan commands. Additionally, the loader manages inserting Vulkan layer libraries, including validation layers between the application and the ICD.

The following components are available in this repository:

Contributing

If you intend to contribute, the preferred work flow is for you to develop your contribution in a fork of this repo in your GitHub account and then submit a pull request. Please see the CONTRIBUTING file in this repository for more details

How to Build and Run

BUILD.md includes directions for building all the components, running the validation tests and running the demo applications.

Information on how to enable the various Validation layers is in layers/README.md.

Architecture and interface information for the loader is in loader/LoaderAndLayerInterface.md.

NOTE: Update Nvidia Drivers

  • A recent glslang change exposed a bug in the texel fetch behavior on Nvidia devices under certain situations.
  • Previously, we reverted the glslang change which exposed it.
  • Nvidia has since resolved the issue, and we are now removing the workaround.
  • Driver installs with the fix are available on their download page, just look for:
  • Linux Drivers starting with version 367.35
  • Windows Drivers starting at version 372.54

License

This work is released as open source under a Apache-style license from Khronos including a Khronos copyright.

See COPYRIGHT.txt for a full list of licenses used in this repository.

Acknowledgements

While this project has been developed primarily by LunarG, Inc; there are many other companies and individuals making this possible: Valve Corporation, funding project development; Google providing significant contributions to the validation layers; Khronos providing oversight and hosting of the project.