From 9914ca800c92e9b3fe768dec4e913a302f3d678d Mon Sep 17 00:00:00 2001 From: jsmall-nvidia Date: Tue, 31 Jul 2018 11:03:53 -0400 Subject: Feature/attributed binding (#621) * Typo fix, and added dxc to command line documentation. * Fix small typos. Added support for Scope to lexer. Fix bug in Token ctor. * Add support for attribute names that are scoped. * Added GLSLBindingAttribute. Make binding work through core.met.slang. * Allow [[gl::binding(binding, set)]] [[vk::binding(binding,set)]] --- docs/command-line-slangc.md | 1 + 1 file changed, 1 insertion(+) (limited to 'docs') diff --git a/docs/command-line-slangc.md b/docs/command-line-slangc.md index 8f27a3dbc..6f7636f19 100644 --- a/docs/command-line-slangc.md +++ b/docs/command-line-slangc.md @@ -85,6 +85,7 @@ For completeness, here are the options that `slangc` currently accepts: * `-pass-through `: Don't actually perform Slang parsing/checking/etc. on the input and instead pass it through more or less modified to the existing compiler ``" * `fxc`: Use the `D3DCompile` API as exposed by `d3dcompiler_47.dll` * `glslang`: Use Slang's internal version of `glslang` as exposed by `slang-glslang.dll` + * 'dxc': Use DirectXShaderCompiler (https://github.com/Microsoft/DirectXShaderCompiler) * These are intended for debugging/testing purposes, when you want to be able to see what these existing compilers do with the "same" input and options * `-profile `: Specify the language "profile" to use. This is a combination of the pipeline stage (vertex, fragment, compute, etc.) and an abstract feature level. E.g., the `ps_5_0` profile specifies the fragment stage, with the Direc3D "Shader Model 5" feature level. To summarize the available profiles: -- cgit v1.2.3