summaryrefslogtreecommitdiffstats
path: root/tests/bindings
diff options
context:
space:
mode:
authorTim Foley <tfoley@nvidia.com>2017-09-11 09:33:46 -0700
committerTim Foley <tfoley@nvidia.com>2017-09-11 14:06:02 -0700
commit2055d540c5dd420448a6924d784d5aed0efcd93d (patch)
tree29167b8abb5001cd3c2803807ec5c8eb3bc2329f /tests/bindings
parent80fb7b05b851e645d821331fdbbcea1add686c9a (diff)
Support IR-based codegen for a few more examples.
The main interesting change here is around support for lowering of calls to "subscript" operations (what a C++ programmer would think of as `operator[]`). An important infrastructure change here was to add an explicit AST-node representation for a "static member expression" which we use whenever a member is looked up in a type as opposed to a value. The implementation of this probably isn't robust yet, but it turns out to be important to be able to tell such cases apart.
Diffstat (limited to 'tests/bindings')
-rw-r--r--tests/bindings/targets-and-uavs-structure.hlsl2
-rw-r--r--tests/bindings/targets-and-uavs.hlsl2
2 files changed, 2 insertions, 2 deletions
diff --git a/tests/bindings/targets-and-uavs-structure.hlsl b/tests/bindings/targets-and-uavs-structure.hlsl
index 4ec64fb75..ffe8ab2a6 100644
--- a/tests/bindings/targets-and-uavs-structure.hlsl
+++ b/tests/bindings/targets-and-uavs-structure.hlsl
@@ -1,4 +1,4 @@
-//TEST(smoke):COMPARE_HLSL: -target dxbc-assembly -profile ps_5_0 -entry main
+//TEST(smoke):COMPARE_HLSL: -use-ir -target dxbc-assembly -profile ps_5_0 -entry main
// Handle the case where the fragment shader output is
// defined a structure, and the semantics are on the sub-fields
diff --git a/tests/bindings/targets-and-uavs.hlsl b/tests/bindings/targets-and-uavs.hlsl
index e5843bed0..674a93050 100644
--- a/tests/bindings/targets-and-uavs.hlsl
+++ b/tests/bindings/targets-and-uavs.hlsl
@@ -1,4 +1,4 @@
-//TEST:COMPARE_HLSL: -target dxbc-assembly -profile ps_5_0 -entry main
+//TEST:COMPARE_HLSL: -use-ir -target dxbc-assembly -profile ps_5_0 -entry main
// Render target outputs (`SV_Target`) and UAVs are treated
// as sharing the same binding slots in HLSL, so we need to