Relax restriction on using link-time types for shader parameters. (#8387)

This change relaxes a previous restriction on link-time types and
constants, so that we now allow them to be used to define shader
parameters.

Doing so will result in a parameter layout that is incomplete prior to
linking. The PR added a test to call the reflection API on a fully
linked program and ensure that we can report correct binding info.

1 files changed, 4 insertions, 1 deletions

diff --git a/tools/slang-test/test-reporter.cpp b/tools/slang-test/test-reporter.cpp
index 3aba10566..00f570b6c 100644
--- a/tools/slang-test/test-reporter.cpp
+++ b/tools/slang-test/test-reporter.cpp
@@ -610,9 +610,9 @@ void TestReporter::message(TestMessageType type, const String& message)
 
     if (canWriteStdError())
     {
+        fprintf(stderr, "[%s] ", m_currentInfo.name.getBuffer());
         if (type == TestMessageType::RunError || type == TestMessageType::TestFailure)
         {
-            fprintf(stderr, "error: ");
             fputs(message.getBuffer(), stderr);
             fprintf(stderr, "\n");
         }
@@ -627,6 +627,9 @@ void TestReporter::message(TestMessageType type, const String& message)
     {
         m_currentMessage << "\n";
     }
+
+    if (m_currentInfo.name.getLength())
+        m_currentMessage << "[" << m_currentInfo.name << "] ";
     m_currentMessage.append(message);
 }