Lei Zhang ddbaf32460 Use standard SPIR-V version scheme for version requirement ... Previously we use symbols in spv_target_env as the minimum version requirements for features. That makes version check implicitly relies on the order of entries in the spv_target_env enum, which also contains client APIs. Instead, we should use the standard scheme for constructing SPIR-V version; and by doing that we can also map client API entries to universial SPIR-V versions.		2018-03-29 12:06:54 -04:00
..
check_code_format.sh	Travis CI: add clang-format check	2017-12-05 08:02:33 -05:00
check_copyright.py	Initial implementation of if conversion	2018-01-25 09:42:00 -08:00
check_symbol_exports.py	Test for pollution of the global namespace	2017-11-23 21:27:21 -05:00
generate_grammar_tables.py	Use standard SPIR-V version scheme for version requirement	2018-03-29 12:06:54 -04:00
generate_language_headers.py	Add asm, dis support for DebugInfo extended instruction set	2017-12-22 09:39:36 -05:00
generate_registry_tables.py	Get vendor tool info from the SPIR-V registry file	2016-12-09 14:01:43 -05:00
generate_vim_syntax.py	Fix generation of Vim syntax file	2018-02-09 17:47:51 -05:00
update_build_version.py	Do nothing if trying to make the current dir	2017-03-20 11:23:35 -04:00