Split the multiple test cases to individual cases.

As the original test framework will do some resource releasing
job at the end of each test runing. If we call multiple tests
in one instance, then we will miss the chance to call those releasing
functions thus may cause some leaking.

Signed-off-by: Zhigang Gong <zhigang.gong@linux.intel.com>
Reviewed-by: Homer Hsing <homer.xing@intel.com>

1 files changed, 15 insertions, 13 deletions

diff --git a/utests/compiler_saturate.cpp b/utests/compiler_saturate.cpp
index db07f4fe..6880df01 100644
--- a/utests/compiler_saturate.cpp
+++ b/utests/compiler_saturate.cpp
@@ -97,16 +97,18 @@ void test(const char *kernel_name)
 
 }
 
-static void compiler_saturate(void)
-{
-  test<int8_t>("test_char");
-  test<uint8_t>("test_uchar");
-  test<int16_t>("test_short");
-  test<uint16_t>("test_ushort");
-  test<int32_t>("test_int");
-  test<uint32_t>("test_uint");
-//  test<int64_t>("test_long");
-//  test<uint64_t>("test_ulong");
-}
-
-MAKE_UTEST_FROM_FUNCTION(compiler_saturate);
+#define compiler_saturate(type, kernel) \
+static void compiler_saturate_ ##type(void)\
+{\
+  test<type>(# kernel);\
+}\
+MAKE_UTEST_FROM_FUNCTION(compiler_saturate_ ## type);
+
+compiler_saturate(int8_t, test_char)
+compiler_saturate(uint8_t, test_uchar)
+compiler_saturate(int16_t, test_short)
+compiler_saturate(uint16_t, test_ushort)
+compiler_saturate(int32_t, test_int)
+compiler_saturate(uint32_t, test_uint)
+//compiler_saturate(int64_t, test_long)
+//compiler_saturate(uint64_t, test_ulong)