Searched refs:ClobberMemory (Results 1 – 9 of 9) sorted by relevance
19 benchmark::ClobberMemory(); in test_basic()28 benchmark::ClobberMemory(); in test_redundant_store()40 benchmark::ClobberMemory(); in test_redundant_read()54 benchmark::ClobberMemory(); in test_redundant_read2()56 benchmark::ClobberMemory(); in test_redundant_read2()
59 benchmark::ClobberMemory(); in BM_InsertValue()73 benchmark::ClobberMemory(); in BM_InsertValueRehash()89 benchmark::ClobberMemory(); in BM_InsertDuplicate()105 benchmark::ClobberMemory(); in BM_EmplaceDuplicate()119 benchmark::ClobberMemory(); in BM_Find()134 benchmark::ClobberMemory(); in BM_FindRehash()148 benchmark::ClobberMemory(); in BM_Rehash()
26 benchmark::ClobberMemory(); in BM_SharedPtrIncDecRef()36 benchmark::ClobberMemory(); in BM_WeakPtrIncDecRef()
89 benchmark::ClobberMemory(); in BM_PathIterateMultipleTimes()110 benchmark::ClobberMemory(); in BM_PathIterateOnce()
142 benchmark::ClobberMemory(); in BM_Hash()
138 ClobberMemory(); in Start()140 ClobberMemory(); in Start()148 ClobberMemory(); in StopAndGetMeasurements()150 ClobberMemory(); in StopAndGetMeasurements()
326 benchmark::ClobberMemory();914 the `benchmark::DoNotOptimize(...)` and `benchmark::ClobberMemory()`949 The second tool for preventing optimizations is `ClobberMemory()`. In essence950 `ClobberMemory()` forces the compiler to perform all pending writes to global953 `ClobberMemory()` prevents the call to `v.push_back(42)` from being optimized963 benchmark::ClobberMemory(); // Force 42 to be written to memory.968 Note that `ClobberMemory()` is only available for GNU or MSVC based compilers.
5 and `ClobberMemory`. In addition there are other functions,
402 inline BENCHMARK_ALWAYS_INLINE void ClobberMemory() { in ClobberMemory() function427 inline BENCHMARK_ALWAYS_INLINE void ClobberMemory() { in ClobberMemory() function439 inline BENCHMARK_ALWAYS_INLINE void ClobberMemory() { _ReadWriteBarrier(); } in ClobberMemory() function