From c16fc84a0071892ea0f4e3c5c70aa101e6400aec Mon Sep 17 00:00:00 2001 From: Tim Foley Date: Mon, 26 Jun 2017 09:07:07 -0700 Subject: Include imported code when generating reflection data - The basic idea is simple: be sure to enumerate code in `__import`ed modules when generating reflection info - Note that we don't currently allow an entry point to appear in an imported module, so we only consider globlal-scope parameters - Although there isn't currently a real implementation of namespacing, I went ahead and ensured that parameters in imported modules are treated as distinct from parameters in the user's code, even if they have the same name. --- tests/reflection/reflect-imported-code.slang | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 tests/reflection/reflect-imported-code.slang (limited to 'tests/reflection/reflect-imported-code.slang') diff --git a/tests/reflection/reflect-imported-code.slang b/tests/reflection/reflect-imported-code.slang new file mode 100644 index 000000000..20beb94b8 --- /dev/null +++ b/tests/reflection/reflect-imported-code.slang @@ -0,0 +1,14 @@ +//TEST_IGNORE_FILE: + +// Imported code used by `reflect-imported-code.hlsl` + +float4 use(float4 val) { return val; }; +float4 use(Texture2D t, SamplerState s) { return t.Sample(s, 0.0); } + +Texture2D t_i; +SamplerState s_i; + +cbuffer C_i +{ + float c_i; +} -- cgit v1.2.3