| commit | a55b1d4519b946547f26d2e7149ed1255dd2980e | [log] [tgz] |
|---|---|---|
| author | Tobin Ehlis <tobine@google.com> | Tue Apr 04 12:23:48 2017 -0600 |
| committer | Tobin Ehlis <tobine@google.com> | Tue Apr 04 16:06:09 2017 -0600 |
| tree | ce412cfb6017945f970ace6165005e050ad265f2 | |
| parent | 67e0ffc5c9600f9d90e2beb5584cd8e6941b0598 [diff] |
scripts:Update unique IDs for spec v1.0.45.1 Another massive update. Totally overhauled the mapping algorithm. The basic outline of the new algorithm is: -Try to map complete error message to prev ID -Then try to map error msg w/o link to prev ID -Finally try to map just core error string (no section) to prev ID -Else assign it a new unique ID See code for complete details. In anticipation of integrated uniqueIDs I took a little liberty with this update in that I didn't attempt to remap EVERY new ID to previous IDs. I did many of them and made sure to account for every previous ID that was implemented. IDs will all be undergoing a one-time change with their integration into the spec anyway so there is little harm in letting non-implemented IDs drift a bit for now and it helps save my sanity. I did add a validation step to the spec.py script to make sure and flag any IDs that previously were implemented and suddenly are no longer in the re-mapped version of IDs. I manually presevered IDs 911 & 912 which get masked from the extension spec. I also had to do some manual updates on an offline spec to keep the parser from breaking on the non-xhtml compliant spec. Command line was: python spec.py -update -remap 92-72:97-77:112-92:116-96:123-103:124-105: 133-114:148-2349:154-133,2:156-135:157-139:204-156:205-155:206-154: 417-269:1189-769:1417-938:1446-965:1448-967:1449-968:1487-974: 2193-1430,5:683-496:684-494:728-529:729-527:1628-1086:1731-1180: 1736-1183:1796-1234:1815-1251
- layers/buffer_validation.cpp[diff]
- layers/core_validation.cpp[diff]
- layers/spec.py[diff]
- layers/vk_validation_error_database.txt[diff]
- layers/vk_validation_error_messages.h[diff]
- tests/layer_validation_tests.cpp[diff]
- build-android/
- cmake/
- common/
- external_revisions/
- include/
- layers/
- loader/
- scripts/
- tests/
- windowsRuntimeInstaller/
- .appveyor.yml
- .clang-format
- .gitignore
- .travis.yml
- BUILD.md
- build_windows_targets.bat
- CMakeLists.txt
- CONTRIBUTING.md
- COPYRIGHT.txt
- LICENSE.txt
- README.md
- update_external_sources.bat
- update_external_sources.sh
Vulkan Ecosystem Components
This project provides Khronos official ICD loader and validation layers for Vulkan developers on Windows and Linux.
CI Build Status
| Platform | Build Status |
|---|---|
| Linux/Android |  |
| Windows |
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:
- Vulkan header files
- ICD Loader
- Validation Layers
- Demos and tests for the loader and validation layers
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.