delta/distcc-git.git/bench/benchmark.py, branch python3

Make the benchmarking script's stdout and stderr line buffered.

2008-08-02T01:30:44+00:00

Reviewers: Craig Silverstein

Tigthen how compilers are located. This overcomes issues on Cygwin. I also

2008-05-29T18:51:41+00:00

changed default C++ compiler to 'c++' instead of 'cxx'. 'c++' is the more common
name I believe.  Witht this change, both compilers must exist for benchmark.py
to run.

REVIEW: csilvers@google.com

Some changes to the benchmark framework to not redo work

2008-05-29T05:38:49+00:00

unnecessarily.  Most prominently, no longer re-run 'tar xf &&
configure' every benchmark run.  Instead, if configure was
successfully executed last benchmark run, just do 'make clean'.  This
is equivalent to what we do now between build runs, when the
repeat-count is > 1.

This feature is not turned on by default, but must be enabled with the
new --force=0 flag.  --force=1 keeps the same behavior as before: we
always re-run configure in each build-directory.  --force=2 adds more
repeat-work than before; in --force=2 mode, we always re-download the
package from the web, even if we had successfully downloaded it
before.

Note that the 'tar' command currently warms the file-cache, which
makes build times more consistent, so there is so cost to setting
--force=0, in terms of the data collected.

Reviewed by klarlund

Normalize the copyright text, to the latest version of the GPLv2 text

2008-05-23T22:24:20+00:00

(typically the only change is in the FSF street address).  Add Google
copyright line in some places it was missing.  Add GPLv2 notice to
avahi patches.

OKed by fergus

Set-up masquerading for benchmarks.

2008-05-23T02:35:03+00:00

Follow the advice of the distcc man page for executing the benchmarks to not
rely on CC and CXX variables by also routing naked calls of 'cc', 'gcc', etc to
a 'farm' of tiny shell scripts.

Also, provide a little wrapper script that does this for people who have to
debug a benchmark build.

This change is convenient for running the benchmark on the linux kernel,
because building the kernel uses naked 'gcc' calls.

Testing:

  Building the linux kernel.

In the benchmark code, make sure a directory exists before cd-ing into

2008-05-20T21:49:52+00:00

it.  This is to handle projects like ACE, which require you to build
from an entirely new directory.

Also fix up an obsolete help-text sentence.

Reviewed by fergus@google.com

Add --output to benchmark.py, to print the final timing summary to a

2008-05-20T05:58:25+00:00

file in addition to stdout.  Also made sure we don't try to access
opt_cc and opt_cxx until after all flags are read, so flag order
doesn't matter.  Finally, fixed indentation so we only print the
default actions when --help is specified (as intended).

Tested by running make benchmark.

Reviewed by klarlund@google.com

Corrent option name.

2008-05-20T03:31:46+00:00

The option is said to be 'distcc', but it's actually implemented as 'dist'.  The
latter is fine with me: we have 'dist' and 'pump', with 'pump' being a more
advanced 'dist'.

Fix a typo in my previous change:

2008-05-12T23:53:45+00:00

  s/parse_opt_compiler/parse_compiler_opt/

Add new options '--cc' and '--cxx' for specifying the paths to use for

2008-05-12T23:02:27+00:00

the C and C++ compilers.

Also, update the help message to document the new format for the
--compiler option.

Reviewers: Craig Silverstein