History log of /external/lldb/tools/lldb-perf/darwin/formatters/formatters.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
4d77c182b3b4fd418ccb488469aa18262bfe481b 15-Apr-2013 Enrico Granata <egranata@apple.com> Sketch test now runs 10 times
Data formatters test outputs stddev

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@179559 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/lldb-perf/darwin/formatters/formatters.cpp
7905badf63cdca9b5eb26a81976edcaf67890c92 11-Apr-2013 Enrico Granata <egranata@apple.com> Updated the line on which to break for the formatters test

Moving over to source-regex might be a good idea, but it’s not what we really want to test. Ideally, we would set a regex breakpoint to find the right line, then delete it and set one by file and line with the right line info from before.

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@179246 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/lldb-perf/darwin/formatters/formatters.cpp
b1b36ec6dcfbe7c7dfa423d50cb7c2296deca68e 01-Apr-2013 Enrico Granata <egranata@apple.com> Integrating option parsing in TestCase for added convenience
To hook it up to individual test cases:
- define GetLongOptions() in your test case class to return something other than NULL (hopefully an array of options :-)
- implement ParseOption() to check for the short option char and do the right thing - return true at the end if you want more options to come your way or false if you don’t
- make sure that your Setup() call takes int& and char**& so that optind post-processing can happen - and call TestCase::Setup from your setup

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@178482 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/lldb-perf/darwin/formatters/formatters.cpp
9de4dec874148d30cc1d4c498d38cd048a8164ca 22-Mar-2013 Greg Clayton <gclayton@apple.com> Much more cleanup on the performance testing infrastructure:
- Added new abtract Results class to keep CoreFoundation out of the tests. There are many subclasses for different settings:
Results::Result::Dictionary
Results::Result::Array
Results::Result::Unsigned
Results::Result::Double
Results::Result::String
- Gauge<T> can now write themselves out via a templatized write to results function:
template <class T>
Results::ResultSP GetResult (const char *description, T value);

- There are four specializations of this so far:
template <>
Results::ResultSP GetResult (const char *description, double value);

template <>
Results::ResultSP GetResult (const char *description, uint64_t value);

template <>
Results::ResultSP GetResult (const char *description, std::string value);

template <>
Results::ResultSP GetResult (const char *description, MemoryStats value);
- Don't emit the virtual memory reading from the task info call as it really doesn't mean much as it includes way too much (shared cache + other stuff we don't have control over)
- Fixed other test cases to build correctly and use the new classes



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@177696 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/lldb-perf/darwin/formatters/formatters.cpp
d3a8d6565ff40fd99533f50a085ace806a9300ee 21-Mar-2013 Greg Clayton <gclayton@apple.com> Add correct file headers to all source files.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@177625 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/lldb-perf/darwin/formatters/formatters.cpp
75fc5a74d95804e2ddc87bcade177640521147e0 21-Mar-2013 Greg Clayton <gclayton@apple.com> Modify code to adhere to LLDB coding conventions.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@177623 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/lldb-perf/darwin/formatters/formatters.cpp
21ac3cbd69627081b1b35f1ff3fa50e72f751455 21-Mar-2013 Enrico Granata <egranata@apple.com> Making a manual mode of operation for measurements, where you can manually call start() and stop() instead of using the function-call syntax
This is especially useful to take measurements that span multiple test steps, or where you need to have different operations fall under the same measurement

An example of use is in the formatters perf test case

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@177597 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/lldb-perf/darwin/formatters/formatters.cpp
3ffb7ed9e634aabc330acdb4a369646caa08c6a2 20-Mar-2013 Enrico Granata <egranata@apple.com> Renaming perf. main files from main.cpp to something meaningful

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@177587 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/tools/lldb-perf/darwin/formatters/formatters.cpp