1. 14 Jun, 2017 3 commits
    • Add ClearRegisteredBenchmark() function. (#402) · b8a2206f
      Eric authored
      * Add ClearRegisteredBenchmark() function.
      
      Since benchmarks can be registered at runtime using the RegisterBenchmark(...)
      functions, it makes sense to have a ClearRegisteredBenchmarks() function too,
      that can be used at runtime to clear the currently registered benchmark and
      re-register an entirely new set.
      
      This allows users to run a set of registered benchmarks, get the output using
      a custom reporter, and then clear and re-register new benchmarks based on the
      previous results.
      
      This fixes issue #400, at least partially.
      
      * Remove unused change
    • Revert "Use NEW settings for CMP0063 policy (#399)" (#401) · d6aacaf4
      Eric authored
      This reverts commit af542061.
    • Use NEW settings for CMP0063 policy (#399) · af542061
      Tim authored
      This removes warnings when using CMake >= 3.3 if you have symbol visibility set.
  2. 05 Jun, 2017 1 commit
  3. 02 Jun, 2017 1 commit
    • Fix #342: DoNotOptimize causes compile errors on older GCC versions. (#398) · 93bfabc8
      Eric authored
      * Fix #342: DoNotOptimize causes compile errors on older GCC versions.
      
      DoNotOptimize uses inline assembly contraints to tell
      the compiler what the type of the input variable. The 'g'
      operand allows the input to be any register, memory, or
      immediate integer operand. However this constraint seems
      to be too weak on older GCC versions, and certain inputs
      will cause compile errors.
      
      This patch changes the constraint to 'X', which is documented
      as "any operand whatsoever is allowed". This appears to fix
      the issues with older GCC versions.
      
      However Clang doesn't seem to like "X", and will attempt
      to put the input into a register even when it can't/shouldn't;
      causing a compile error. However using "g" seems to work like
      "X" with GCC, so for this reason Clang still uses "g".
      
      * Try alternative formulation to placate GCC
  4. 23 May, 2017 1 commit
  5. 22 May, 2017 2 commits
  6. 04 May, 2017 1 commit
  7. 03 May, 2017 1 commit
  8. 02 May, 2017 16 commits
  9. 01 May, 2017 7 commits
  10. 29 Apr, 2017 7 commits