Gemm Universal unit tests for MainloopIntelW8A8 API

[rishi-yadav]

Unit tests for MainloopIntelW8A8 FP8 GEMM operations on Intel Xe

Comprehensive test coverage for Intel GPU FP8 GEMM kernels including:

• LLM workloads: LLaMA2-7B, Mistral-7B configurations
• Parallelization: Tensor/model parallel scenarios
• Batch sizes: Micro-batch (4x) to large batch (32x)
• Matrix shapes: Small (64²) to large (2048²), tall/wide matrices
• Edge cases: Large K/N dimensions

Tests validate MainloopIntelW8A8 dispatch policy with FP8→FP32 precision on Intel Xe XMX architecture.

[Copilot]

Pull Request Overview

This PR adds comprehensive unit test coverage for Intel GPU FP8 GEMM operations using the MainloopIntelW8A8 dispatch policy. The tests validate FP8→FP32 matrix multiplication kernels on Intel Xe XMX architecture across various workload scenarios.

Key changes:

• Added 14 unit tests covering LLM model configurations (LLaMA2-7B, Mistral-7B), parallelization strategies, and various matrix dimensions
• Introduced new TestXe overload accepting explicit batch parameter for batched GEMM operations
• Integrated new test file into CMake build system

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
gemm_universal_fp8_fp8_fp32_tensor_op_f32_xe_models.cpp	New test file with 14 test cases covering model-specific and edge-case GEMM configurations
gemm_testbed_3x.hpp	Added TestXe overload with explicit batch size parameter and enhanced error reporting
CMakeLists.txt	Added new test file to SYCL-enabled build targets

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Using 'EXPECT_TRUE(false)' is an anti-pattern. Replace with 'FAIL()' or 'ADD_FAILURE()' for clearer intent and better test failure messages in Google Test.

Suggested change

	EXPECT_TRUE(false) << "TestXe: testbed.run threw an exception: " << e.what();
	throw;
	}
	catch (...) {
	EXPECT_TRUE(false) << "TestXe: testbed.run threw an unknown exception";
	FAIL() << "TestXe: testbed.run threw an exception: " << e.what();
	throw;
	}
	catch (...) {
	FAIL() << "TestXe: testbed.run threw an unknown exception";

[rolandschulz]

copilot is wrong with FAIL. ADD_FAILURE might be slightly better but I'm OK either way.

[Copilot]

Using 'EXPECT_TRUE(false)' is an anti-pattern. Replace with 'FAIL()' or 'ADD_FAILURE()' for clearer intent and better test failure messages in Google Test.

Suggested change

	EXPECT_TRUE(false) << "TestXe: testbed.run threw an exception: " << e.what();
	throw;
	}
	catch (...) {
	EXPECT_TRUE(false) << "TestXe: testbed.run threw an unknown exception";
	FAIL() << "TestXe: testbed.run threw an exception: " << e.what();
	throw;
	}
	catch (...) {
	FAIL() << "TestXe: testbed.run threw an unknown exception";