1
92%
master: 92%

Ran 29 Aug 2018 06:15PM UTC

Files 36

Run time 4s

Badge

Embed ▾

Committed 29 Aug 2018 06:11PM UTC coverage: 87.635% (+0.7%) from 86.887%

Job # COMPILER=g++ C_COMPILER=gcc BUILD_TYPE=Coverage

Build Type

push

travis-ci

Committed by

web-flow

Commit Message

Counter(): add 'one thousand' param. (#657)

* Counter(): add 'one thousand' param.

Needed for https://github.com/google/benchmark/pull/654

Custom user counters are quite custom. It is not guaranteed
that the user *always* expects for these to have 1k == 1000.
If the counter represents bytes/memory/etc, 1k should be 1024.

Some bikeshedding points:
1. Is this sufficient, or do we really want to go full on
   into custom types with names?
   I think just the '1000' is sufficient for now.
2. Should there be a helper benchmark::Counter::Counter{1000,1024}()
   static 'constructor' functions, since these two, by far,
   will be the most used?
3. In the future, we should be somehow encoding this info into JSON.

* Counter(): use std::pair<> to represent 'one thousand'

* Counter(): just use a new enum with two values 1000 vs 1024.

Simpler is better. If someone comes up with a real reason
to need something more advanced, it can be added later on.

* Counter: just store the 1000 or 1024 in the One_K values directly

* Counter: s/One_K/OneK/

Run Details

1538 of 1755 relevant lines covered (87.64%)

4988607.5 hits per line

google / benchmark / 1754 / 1
92%
master: 92%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1754.1 (COMPILER=g++ C_COMPILER=gcc BUILD_TYPE=Coverage)

google / benchmark / 1754 / 1 92% master: 92%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1754.1 (COMPILER=g++ C_COMPILER=gcc BUILD_TYPE=Coverage)

google / benchmark / 1754 / 1
92%
master: 92%

README BADGES
x