From 004fe27a52b7952111ad7e749397aeff499de7ed Mon Sep 17 00:00:00 2001
From: skallweitNV <64953474+skallweitNV@users.noreply.github.com>
Date: Fri, 7 Jun 2024 09:28:16 +0200
Subject: Metal compute tests (#4292)

---
 tests/bugs/dxbc-double-problem.slang | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'tests/bugs/dxbc-double-problem.slang')

diff --git a/tests/bugs/dxbc-double-problem.slang b/tests/bugs/dxbc-double-problem.slang
index 441000f63..9daa28a9f 100644
--- a/tests/bugs/dxbc-double-problem.slang
+++ b/tests/bugs/dxbc-double-problem.slang
@@ -3,6 +3,7 @@
 //TEST(compute):COMPARE_COMPUTE_EX:-cpu -compute -output-using-type -shaderobj
 //TEST(compute):COMPARE_COMPUTE_EX:-dx12 -compute -use-dxil -output-using-type -shaderobj
 //DISABLE_TEST(compute):COMPARE_COMPUTE_EX:-dx12 -compute -output-using-type -shaderobj
+//DISABLE_TEST(compute):COMPARE_COMPUTE:-slang -shaderobj -mtl
 
 // The problem this test shows is around handling of double with dxbc on D3D12. In that combination
 // this code does not write the correct value into the first element - it appears as 0, where 
@@ -27,4 +28,4 @@ void computeMain(uint3 dispatchThreadID : SV_DispatchThreadID)
     outputBuffer[1] = pi;
     outputBuffer[2] = pi_180;
     outputBuffer[3] = w;
-}
\ No newline at end of file
+}
-- 
cgit v1.2.3