From 43728fbda5b9af19eded18fe82ca67b66cc6d0f7 Mon Sep 17 00:00:00 2001 From: Yong He Date: Fri, 22 Nov 2024 15:14:48 -0800 Subject: Don't treat StrcturedBuffer as a specializable param. (#5645) * Don't treat StrcturedBuffer as a specializable param. * Fix RHI. --- tests/language-feature/interfaces/empty-type-conformance.slang | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'tests/language-feature/interfaces') diff --git a/tests/language-feature/interfaces/empty-type-conformance.slang b/tests/language-feature/interfaces/empty-type-conformance.slang index 9fee04607..ae529a496 100644 --- a/tests/language-feature/interfaces/empty-type-conformance.slang +++ b/tests/language-feature/interfaces/empty-type-conformance.slang @@ -1,5 +1,3 @@ -// Test that we allow empty type conformances. - //TEST(compute):COMPARE_COMPUTE_EX(filecheck-buffer=CHECK):-dx11 -compute -output-using-type //TEST(compute):COMPARE_COMPUTE_EX(filecheck-buffer=CHECK):-vk -compute -output-using-type @@ -18,6 +16,8 @@ StructuredBuffer inBuffer; //TEST_INPUT: set outputBuffer = out ubuffer(data=[0 0 0 0], stride=4); RWStructuredBuffer outputBuffer; +//TEST_INPUT: type_conformance TestImplementation:TestInterface=0 + [shader("compute")] [numthreads(1, 1, 1)] void computeMain(uint3 dispatchThreadID: SV_DispatchThreadID) -- cgit v1.2.3