Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / vulkan-validation-layers / 8bef8ee56e2acc604bf28332a6b536233ee132e5
commit8bef8ee56e2acc604bf28332a6b536233ee132e5[log] [tgz]
authorTony Barbour <tony@LunarG.com>Fri May 22 09:44:58 2015 -0600
committerTony Barbour <tony@LunarG.com>Tue Jun 02 14:40:18 2015 -0600
treefca6be6190559cb3636d292b168102b7f64fe9b2
parent43cdc9557a9fd39cc3ce08259def0827dad9cf91 [diff]
tests: Clean up some MSVC++ compiler warnings

Known issues running tests on Windows:

- Compiler warnings from gtest that we haven’t spent the time to figure out

- Tests don’t run in place - you need to have them in the same directory with vulkan.dll,
  gtest.dll, and if MSVC++ is not installed, the MSVC++ runtime dlls.  If you want to use
  the --compare-images option to vk_render_tests, you will need the “golden”
  folder with golden images.

- vk_layer_validation_tests will fail unless you specify VK_LAYER_NAMES as Validation
  in the registry or  environment. You will also need to specify VK_LAYERS_PATH to point
  to the layer dlls.   The mismatched type validation test will fail regardless as the
  check it is testing for did not make it into the SDK branch

- Known issue of parameter checker for CreateDepthStencilView expecting msaaResolveSubresource
  to be valid even if msaa isn’t active

- Problem with runtime assert or hang in shader tracker - for now just remove the
  shader checker files from your VK_LAYERS_PATH location.
6 files changed
tree: fca6be6190559cb3636d292b168102b7f64fe9b2
  1. cmake/
  2. demos/
  3. docs/
  4. icd/
  5. include/
  6. layers/
  7. libs/
  8. loader/
  9. tests/
  10. tools/
  11. .gitignore
  12. BUILD.md
  13. CMakeLists.txt
  14. LICENSE.txt
  15. README.md
  16. update_external_sources.sh
  17. vk-generate.py
  18. vk-layer-generate.py
  19. vk_helper.py
  20. vulkan.py
README.md

Explicit GL (VK) Ecosystem Components

Version 0.8, 04 Feb 2015

This project provides open source tools for VK Developers.

Introduction

VK is an Explicit API, enabling direct control over how GPUs actually work. No validation, shader recompilation, memory management or synchronization is done inside an VK driver. Applications have full control and responsibility. Any errors in how VK is used are likely to result in a crash. This project provides layered utility libraries to ease development and help guide developers to proven safe patterns.

New with VK in an extensible layered architecture that enables significant innovation in tools:

  • Cross IHV support enables tools vendors to plug into a common, extensible layer architecture
  • Layered tools during development enable validating, debugging and profiling without production performance impact
  • Modular validation architecture encourages many fine-grained layers--and new layers can be added easily
  • Encourages open community of tool developers: led by Valve, LunarG, Codeplay and others
  • Customized interactive debugging and validation layers will be available together with first drivers

The components here are being shared with the Khronos community to provide insights into the specification as we approach an alpha header, and to assists those doing demos for GDC.

The following components are available:

New

  • Updated loader, driver, demos, tests and many tools to use "alpha" vulkan.h (~ version 47). Supports new resource binding model, memory allocation, pixel FORMATs and other updates. APIDump layer is working with these new API elements. Glave can trace and replay the cube and tri demos. Other layers in progress.
  • Warning: Recent versions of 14.10 have REMOVED DRI 3.
    Version: 2:2.99.914-1~exp1ubuntu4.1 is known to work.

Prior updates

  • VK API trace and capture tools. See tools/glave/README.md for details.
  • Sample driver now supports multiple render targets. Added TriangleMRT to test that functionality.
  • Added VK_SLOT_SHADER_TEXTURE_RESOURCE to vulkan.h as a descriptor slot type to work around confusion in GLSL between textures and buffers as shader resources.
  • Misc. fixes for layers and Intel sample driver
  • Added mutex to APIDump, APIDumpFile and DrawState to prevent apparent threading issues using printf
  • Fix support for {Fill,Copy}Memory
  • MemTracker can report issues to application via debug callback
  • Update test infrastructure to improve ease of writing new tests. Add image comparison feature for regression testing. Requires ImageMagick library.
  • Misc. fixes to demos, layers and Intel sample driver
  • Added mutex to APIDump, APIDumpFile and DrawState to prevent apparent threading issues using printf
  • Fix support for {Fill,Copy}Memory
  • MemTracker can report issues to application via debug callback
  • Update test infrastructure to improve ease of writing new tests. Add image comparison feature for regression testing. Requires ImageMagick library.
  • Misc. fixes to demos, layers and Intel sample driver

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 Debug and Validation layers is in layers/README.md.

References

This version of the components are written based on the following preliminary specs and proposals:

License

This work is intended to be released as open source under a BSD-style license once the VK specification is public. Until that time, this work is covered by the Khronos NDA governing the details of the VK API.

Acknowledgements

While this project is being developed by LunarG, Inc; there are many other companies and individuals making this possible: Valve Software, funding project development; Intel Corporation, providing full hardware specifications and valuable technical feedback; AMD, providing VK spec editor contributions; ARM, contributing a Chairman for this working group within Khronos; Nvidia, providing an initial co-editor for the spec; Qualcomm for picking up the co-editor's chair; and Khronos, for providing hosting within GitHub.

Contact

If you have questions or comments about this driver; or you would like to contribute directly to this effort, please contact us at VK@LunarG.com; or if you prefer, via the GL Common mailing list: gl_common@khronos.org