This complies with Fuchsia's default_warnings config, which contains
"-Wnewline-eof".

Change-Id: I5bc4b5d99773bb728c5af93283e03c7c57787fb8

Change-Id: I4edc4c73b035c5682cf45c3f129e7331b3d6b4a1

Change-Id: Id27282ba9972af7b34cba887981820e7c16c1c7d

Upstream obtained from existing git remote

SEC-17

Change-Id: Ia338d1e30ab79bea4ffa2e51ca2c16ffcb767986

They're legacy POSIX interfaces that don't make sense on Fuchsia.

Change-Id: I77c5c33bbf658c3c391b5d1a7e9c16c3d908ebd8

Change-Id: I6449171a37a084a75de1ba486ae2b0592e3c9242

Change-Id: I1e7e5929091b534c0c99b236910c76308cba5317

This patch cleans up a number of issues with how compare_bench.py handled
the command line arguments.

* Use the 'argparse' python module instead of hand rolled parsing. This gives
  better usage messages.

* Add diagnostics for certain --benchmark flags that cannot or should not
  be used with compare_bench.py (eg --benchmark_out_format=csv).

* Don't override the user specified --benchmark_out flag if it's provided.

In future I would like the user to be able to capture both benchmark output
files, but this change is big enough for now.

This fixes issue #313.

Fixes #306

* Test bytes_per_second and items_per_second.

* Test SetLabel.

* Reformat.

* Make State::error_occurred_ private.

* Fix tests with floats.

* Merge private blocks

* fix working on mac clock_gettime

* Comment fixme

* Auto-detect whether to produce colorized output

Rename --color_print to --benchmark_color for consistency with the other
flags (and Google Test). Old flag name is kept around for compatibility.

The --benchmark_color/--color_print flag takes a third option, "auto",
which is the new default. In this mode, we attempt to auto-detect
whether to produce colorized output. (The logic for deciding whether to
use colorized output was lifted from GTest:
<https://github.com/google/googletest/blob/master/googletest/src/gtest.cc#L2925>.)

* Update CONTRIBUTORS, AUTHORS

If a reporter's output stream isn't line-buffered (e.g. it's not writing
to a terminal) then it can be some time before a write to it becomes
visible.

This is problematic if, say, you're wanting to use tail -f to view the
file written to via --benchmark_out. Or if the application crashes,
leaving you with no results.

Addressed by flushing the reporters' output streams whenever we invoke
methods that may write to them.

* Cleanup the code for generating and running benchmarks

* Rework calculation of real/manual time

* Add back TSAN builder

* Refactor benchmark.cc into benchmark_register.cc and benchmark_run.cc

The benchmark.cc file is getting really big and it contains a bunch of
unrelated components. This patch separates the files into two separate
parts. The "runtime" parts and the "registration" parts.

This patch also removes the PIMPL used by Benchmark. Previously we couldn't
have STL types in the interface but now we can. Therefore there is no reason
to keep BenchmarkImp.

* add missing include

* rework windows timers again

* Guard timespec on older Windows versions

* Remove old thread safety annotation workarounds

* add additive thread range

* add test