From e36c20ffda59a965b29d40037bb02026c7f43db9 Mon Sep 17 00:00:00 2001 From: Chris Date: Thu, 29 Jun 2017 09:51:44 +0100 Subject: [PATCH] Fix timing issues found in "Flash - clock and cache test" ARMCC seemed to be inlining time_cpu_cycles() but with a different number of clock cycles in the loop, GCC worked fine. --- TESTS/mbed_hal/flash/functional_tests/main.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TESTS/mbed_hal/flash/functional_tests/main.cpp b/TESTS/mbed_hal/flash/functional_tests/main.cpp index d2bf288467..1c933ecdd1 100644 --- a/TESTS/mbed_hal/flash/functional_tests/main.cpp +++ b/TESTS/mbed_hal/flash/functional_tests/main.cpp @@ -53,7 +53,7 @@ static void erase_range(flash_t *flash, uint32_t addr, uint32_t size) } } -static int time_cpu_cycles(uint32_t cycles) +__attribute__((noinline)) static int time_cpu_cycles(uint32_t cycles) { Timer timer; timer.start();