From 6c046992a71e672df504a0101cddf6f2f2e90601 Mon Sep 17 00:00:00 2001
From: Mulugeta Mammo <mulugeta.mammo@intel.com>
Date: Tue, 4 Feb 2025 09:45:44 -0800
Subject: [PATCH] Fix the order of parameters in
 bench_scalar_quantizer_distance. (#4159)

Summary:
I believe the order of the parameters was not intended to be that way. This PR fixes it.

Pull Request resolved: https://github.com/facebookresearch/faiss/pull/4159

Reviewed By: mengdilin

Differential Revision: D69073195

Pulled By: junjieqi

fbshipit-source-id: bfb62aa7536deeda73bee32f2de3cd7a8142bb13
---
 perf_tests/bench_scalar_quantizer_distance.cpp | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/perf_tests/bench_scalar_quantizer_distance.cpp b/perf_tests/bench_scalar_quantizer_distance.cpp
index 14945c58c..8a32d69c7 100644
--- a/perf_tests/bench_scalar_quantizer_distance.cpp
+++ b/perf_tests/bench_scalar_quantizer_distance.cpp
@@ -23,8 +23,8 @@ DEFINE_uint32(iterations, 20, "iterations");
 static void bench_distance(
         benchmark::State& state,
         ScalarQuantizer::QuantizerType type,
-        int n,
-        int d) {
+        int d,
+        int n) {
     std::vector<float> x(d * n);
 
     float_rand(x.data(), d * n, 12345);