Workaround bug in IGC

Signed-off-by: Andrew Savonichev <[email protected]>

Author: Andrew Savonichev

sycl/source/detail/devicelib/fallback-cassert.cpp

@@ -29,7 +29,9 @@ extern "C" void __devicelib_assert_fail(
   __spirv_ocl_printf(
       assert_fmt,
       file, (int32_t)line,
-      (func) ? func : "<unknown function>",
+      // WORKAROUND: IGC does not handle this well
+      // (func) ? func : "<unknown function>",
+      func,
       gid0, gid1, gid2,
       lid0, lid1, lid2,
       expr);

sycl/test/devicelib/assert-windows.cpp

@@ -16,7 +16,7 @@
 //
 // RUN: env SYCL_PI_TRACE=1 SYCL_DEVICELIB_INHIBIT_NATIVE=1 SYCL_DEVICE_TYPE=CPU %t.out >%t.stdout.fallback 2>%t.stderr.fallback
 // RUN: FileCheck %s --check-prefix=CHECK-MESSAGE --input-file %t.stdout.fallback
-// CHECK-MESSAGE: {{.*}}assert-windows.cpp:{{[0-9]+}}: <unknown function>: local id: [{{[0-3]}},0,0], global id: [{{[0-3]}},0,0] Assertion `accessorC[wiID] == 0 && "Invalid value"` failed.
+// CHECK-MESSAGE: {{.*}}assert-windows.cpp:{{[0-9]+}}: (null): local id: [{{[0-3]}},0,0], global id: [{{[0-3]}},0,0] Assertion `accessorC[wiID] == 0 && "Invalid value"` failed.
 //
 // RUN: FileCheck %s --input-file %t.stdout.fallback --check-prefix=CHECK-FALLBACK
 // CHECK-FALLBACK: ---> piProgramLink