Add a note to clarify pretranspose option in GEMM and GEMMLowp fixtures

Signed-off-by: Adnan AlSinan <adnan.alsinan@arm.com>
Change-Id: Ie65f9096a75610dc20ffbb25dc43fd2f632f2f03
Reviewed-on: https://review.mlplatform.org/c/ml/ComputeLibrary/+/7530
Tested-by: Arm Jenkins <bsgcomp@arm.com>
Reviewed-by: Gunes Bayir <gunes.bayir@arm.com>
Comments-Addressed: Arm Jenkins <bsgcomp@arm.com>

1 files changed, 4 insertions, 0 deletions

diff --git a/tests/validation/fixtures/GEMMLowpFixture.h b/tests/validation/fixtures/GEMMLowpFixture.h
index 3f83cc92f1..3da4c02f6d 100644
--- a/tests/validation/fixtures/GEMMLowpFixture.h
+++ b/tests/validation/fixtures/GEMMLowpFixture.h
@@ -191,6 +191,10 @@ SimpleTensor<int32_t> compute_gemmlowp_reference(const TensorShape &shape_a, con
     fill(b, 1);
 
     // Transpose reference if required
+    /* Note: Assuming the usual batch matmul dimensions A = (B x M x K), B = (B x K x N), if pretranspose_A is set to true, then A is assumed to be (B x K x M),
+       therefore, A must be pre-transposed before passing it to the fixture. And, we transpose A again in the fixture to make it (B x M x K)
+       in order to be able to call reference implementation that works with (B x M x K) input.
+       Similarly, if pretranspose_B is set to true, then B is assumed to be (B x N x K), B must be pre-transposed before passing it to the fixture. */
     if(pretranspose_A)
     {
         transpose_matrix<TI>(a, a_transposed);