shylie/llvm-project
1
0
Fork 0
Code Issues Pull Requests Actions 6 Packages Projects Releases Wiki Activity
114,121 Commits 1,713 Branches 298 Tags
Commit Graph

8 Commits

Author SHA1 Message Date
Johnny Chen
0affe0213d Print out the stopwatch (which contains laps, total elapsed time, and average) 
instead of just the average.

llvm-svn: 136932
 2011-08-04 22:05:36 +00:00
Johnny Chen
c99dd97fc5 Fix typos. 
llvm-svn: 136809
 2011-08-03 20:40:35 +00:00
Johnny Chen
a8d4df429a Add license header comment. 
llvm-svn: 136808
 2011-08-03 20:39:26 +00:00
Johnny Chen
aaa82ff9ad Add the real benchmarks comparing lldb against gdb for repeated expression evaluations. 
Modify lldbbench.py so that lldbtest.line_number() utility function is available to
BenchBase client as just line_number(), and modify lldbtest.py so that self.lldbExec
(the full path for the 'lldb' executable) is available to BenchBase client as well.

An example run of the test case on my MacBook Pro running Lion:

1: test_compare_lldb_to_gdb (TestRepeatedExprs.RepeatedExprsCase)
   Test repeated expressions with lldb vs. gdb. ... 
lldb_avg: 0.204339
gdb_avg: 0.205721
lldb_avg/gdb_avg: 0.993284
ok

llvm-svn: 136740
 2011-08-02 22:54:37 +00:00
Johnny Chen
da0384c90e Simple renaming: self.swatch -> self.stopwatch. 
llvm-svn: 136666
 2011-08-02 00:50:55 +00:00
Johnny Chen
2352af85f9 Add a Stopwatch utility class to lldbench.py module and initialize an instance of 
Stopwatch (self.swatch) within the BenchBase's setUp() instance method to be available
to all the child classes.

Use self.swatch to measure elapsed time in TestRepeatedExprs.py, which needs to be
modified later on to actually measure repeated expression evaluations within the
context of lldb as well as gdb.

llvm-svn: 136664
 2011-08-02 00:43:09 +00:00
Johnny Chen
985e740cd9 Add an abstract base class called BenchBase to be inherited by benchmark tests. 
Modify the example TestRepeatedExprs.py to use BenchBase, instead.

llvm-svn: 136649
 2011-08-01 21:13:26 +00:00
Johnny Chen
5ccbccfce0 Add a @benchmarks_test decorator for test method we want to categorize as benchmarks test. 
The test driver now takes an option "+b" which enables to run just the benchmarks tests.
By default, tests decorated with the @benchmarks_test decorator do not get run.

Add an example benchmarks test directory which contains nothing for the time being,
just to demonstrate the @benchmarks_test concept.

For example,

$ ./dotest.py -v benchmarks

...

----------------------------------------------------------------------
Collected 2 tests

1: test_with_gdb (TestRepeatedExprs.RepeatedExprssCase)
   Test repeated expressions with gdb. ... skipped 'benchmarks tests'
2: test_with_lldb (TestRepeatedExprs.RepeatedExprssCase)
   Test repeated expressions with lldb. ... skipped 'benchmarks tests'

----------------------------------------------------------------------
Ran 2 tests in 0.047s

OK (skipped=2)
$ ./dotest.py -v +b benchmarks

...

----------------------------------------------------------------------
Collected 2 tests

1: test_with_gdb (TestRepeatedExprs.RepeatedExprssCase)
   Test repeated expressions with gdb. ... running test_with_gdb
benchmarks result for test_with_gdb
ok
2: test_with_lldb (TestRepeatedExprs.RepeatedExprssCase)
   Test repeated expressions with lldb. ... running test_with_lldb
benchmarks result for test_with_lldb
ok

----------------------------------------------------------------------
Ran 2 tests in 0.270s

OK

Also mark some Python API tests which are missing the @python_api_test decorator.

llvm-svn: 136553
 2011-07-30 01:39:58 +00:00