maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lldb/tools/lldb-perf/darwin/formatters/formatters.cpp

247 lines
9.7 KiB
C++
Raw Normal View History

Add correct file headers to all source files. llvm-svn: 177625
2013-03-21 11:39:51 +08:00
//===-- formatters.cpp ------------------------------------------*- C++ -*-===//
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
//
Add correct file headers to all source files. llvm-svn: 177625
2013-03-21 11:39:51 +08:00
// The LLVM Compiler Infrastructure
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
//
Add correct file headers to all source files. llvm-svn: 177625
2013-03-21 11:39:51 +08:00
// This file is distributed under the University of Illinois Open Source
// License. See LICENSE.TXT for details.
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
//
Add correct file headers to all source files. llvm-svn: 177625
2013-03-21 11:39:51 +08:00
//===----------------------------------------------------------------------===//
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
#include <CoreFoundation/CoreFoundation.h>
#include "lldb-perf/lib/Timer.h"
#include "lldb-perf/lib/Metric.h"
#include "lldb-perf/lib/Measurement.h"
#include "lldb-perf/lib/TestCase.h"
#include "lldb-perf/lib/Xcode.h"
#include <iostream>
#include <unistd.h>
#include <fstream>
Code cleanup: - don't use preprocessor macros - use switch statements - don't put anything in the lldb namespace, use "lldb_perf" namespace. - Pass the action struct into each TestStep() for each step fill in - Modify the ActionWanted class to have accessors to make the continue, next, finish, kill instead of using preproc macros llvm-svn: 177332
2013-03-19 06:34:00 +08:00
using namespace lldb_perf;
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
class FormattersTest : public TestCase
{
public:
FormattersTest () : TestCase()
{
m_dump_std_vector_measurement = CreateTimeMeasurement([] (SBValue value) -> void {
Code cleanup: - don't use preprocessor macros - use switch statements - don't put anything in the lldb namespace, use "lldb_perf" namespace. - Pass the action struct into each TestStep() for each step fill in - Modify the ActionWanted class to have accessors to make the continue, next, finish, kill instead of using preproc macros llvm-svn: 177332
2013-03-19 06:34:00 +08:00
lldb_perf::Xcode::FetchVariable (value,1,false);
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
}, "std-vector", "time to dump an std::vector");
m_dump_std_list_measurement = CreateTimeMeasurement([] (SBValue value) -> void {
Code cleanup: - don't use preprocessor macros - use switch statements - don't put anything in the lldb namespace, use "lldb_perf" namespace. - Pass the action struct into each TestStep() for each step fill in - Modify the ActionWanted class to have accessors to make the continue, next, finish, kill instead of using preproc macros llvm-svn: 177332
2013-03-19 06:34:00 +08:00
lldb_perf::Xcode::FetchVariable (value,1,false);
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
}, "std-list", "time to dump an std::list");
m_dump_std_map_measurement = CreateTimeMeasurement([] (SBValue value) -> void {
Code cleanup: - don't use preprocessor macros - use switch statements - don't put anything in the lldb namespace, use "lldb_perf" namespace. - Pass the action struct into each TestStep() for each step fill in - Modify the ActionWanted class to have accessors to make the continue, next, finish, kill instead of using preproc macros llvm-svn: 177332
2013-03-19 06:34:00 +08:00
lldb_perf::Xcode::FetchVariable (value,1,false);
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
}, "std-map", "time to dump an std::map");
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 llvm-svn: 177597
2013-03-21 07:01:28 +08:00
// use this in manual mode
m_dump_std_string_measurement = CreateTimeMeasurement([] () -> void {
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
}, "std-string", "time to dump an std::string");
m_dump_nsstring_measurement = CreateTimeMeasurement([] (SBValue value) -> void {
Code cleanup: - don't use preprocessor macros - use switch statements - don't put anything in the lldb namespace, use "lldb_perf" namespace. - Pass the action struct into each TestStep() for each step fill in - Modify the ActionWanted class to have accessors to make the continue, next, finish, kill instead of using preproc macros llvm-svn: 177332
2013-03-19 06:34:00 +08:00
lldb_perf::Xcode::FetchVariable (value,0,false);
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
}, "ns-string", "time to dump an NSString");
m_dump_nsarray_measurement = CreateTimeMeasurement([] (SBValue value) -> void {
Code cleanup: - don't use preprocessor macros - use switch statements - don't put anything in the lldb namespace, use "lldb_perf" namespace. - Pass the action struct into each TestStep() for each step fill in - Modify the ActionWanted class to have accessors to make the continue, next, finish, kill instead of using preproc macros llvm-svn: 177332
2013-03-19 06:34:00 +08:00
lldb_perf::Xcode::FetchVariable (value,1,false);
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
}, "ns-array", "time to dump an NSArray");
m_dump_nsdictionary_measurement = CreateTimeMeasurement([] (SBValue value) -> void {
Code cleanup: - don't use preprocessor macros - use switch statements - don't put anything in the lldb namespace, use "lldb_perf" namespace. - Pass the action struct into each TestStep() for each step fill in - Modify the ActionWanted class to have accessors to make the continue, next, finish, kill instead of using preproc macros llvm-svn: 177332
2013-03-19 06:34:00 +08:00
lldb_perf::Xcode::FetchVariable (value,1,false);
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
}, "ns-dictionary", "time to dump an NSDictionary");
m_dump_nsset_measurement = CreateTimeMeasurement([] (SBValue value) -> void {
Code cleanup: - don't use preprocessor macros - use switch statements - don't put anything in the lldb namespace, use "lldb_perf" namespace. - Pass the action struct into each TestStep() for each step fill in - Modify the ActionWanted class to have accessors to make the continue, next, finish, kill instead of using preproc macros llvm-svn: 177332
2013-03-19 06:34:00 +08:00
lldb_perf::Xcode::FetchVariable (value,1,false);
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
}, "ns-set", "time to dump an NSSet");
m_dump_nsbundle_measurement = CreateTimeMeasurement([] (SBValue value) -> void {
Code cleanup: - don't use preprocessor macros - use switch statements - don't put anything in the lldb namespace, use "lldb_perf" namespace. - Pass the action struct into each TestStep() for each step fill in - Modify the ActionWanted class to have accessors to make the continue, next, finish, kill instead of using preproc macros llvm-svn: 177332
2013-03-19 06:34:00 +08:00
lldb_perf::Xcode::FetchVariable (value,1,false);
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
}, "ns-bundle", "time to dump an NSBundle");
m_dump_nsdate_measurement = CreateTimeMeasurement([] (SBValue value) -> void {
Code cleanup: - don't use preprocessor macros - use switch statements - don't put anything in the lldb namespace, use "lldb_perf" namespace. - Pass the action struct into each TestStep() for each step fill in - Modify the ActionWanted class to have accessors to make the continue, next, finish, kill instead of using preproc macros llvm-svn: 177332
2013-03-19 06:34:00 +08:00
lldb_perf::Xcode::FetchVariable (value,0,false);
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
}, "ns-date", "time to dump an NSDate");
}
virtual
~FormattersTest ()
{
}
More cleanup on the lldb-perf code: - TestCase.m_thread is now filled in with the first thread that has a valid stop reason. This eliminates the need for the SelectMyThread() functions. - The first thread that stops for a reason is also set as the selected thread in the process in case any command line commands are run. - Changed launch over to take a SBLaunchInfo parameter so that the launch function doesn't keep getting new arguments as they are needed. - TestCase::Setup() and TestCase::Launch(SBLaunchInfo) now return bool to indicate success of setup and launch. - ActionWanted::Next(SBThread) was renamed to ActionWanted::StepOver(SBThread) - ActionWanted::Finish(SBThread) was renamed to ActionWanted::StepOut(SBThread) llvm-svn: 177376
2013-03-19 12:41:22 +08:00
virtual bool
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 llvm-svn: 178482
2013-04-02 02:02:25 +08:00
Setup (int& argc, const char**& argv)
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
{
m_app_path.assign(argv[1]);
m_out_path.assign(argv[2]);
m_target = m_debugger.CreateTarget(m_app_path.c_str());
m_target.BreakpointCreateByName("main");
More cleanup on the lldb-perf code: - TestCase.m_thread is now filled in with the first thread that has a valid stop reason. This eliminates the need for the SelectMyThread() functions. - The first thread that stops for a reason is also set as the selected thread in the process in case any command line commands are run. - Changed launch over to take a SBLaunchInfo parameter so that the launch function doesn't keep getting new arguments as they are needed. - TestCase::Setup() and TestCase::Launch(SBLaunchInfo) now return bool to indicate success of setup and launch. - ActionWanted::Next(SBThread) was renamed to ActionWanted::StepOver(SBThread) - ActionWanted::Finish(SBThread) was renamed to ActionWanted::StepOut(SBThread) llvm-svn: 177376
2013-03-19 12:41:22 +08:00
SBLaunchInfo launch_info(argv);
return Launch (launch_info);
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
}
void
DoTest ()
{
More cleanup on the lldb-perf code: - TestCase.m_thread is now filled in with the first thread that has a valid stop reason. This eliminates the need for the SelectMyThread() functions. - The first thread that stops for a reason is also set as the selected thread in the process in case any command line commands are run. - Changed launch over to take a SBLaunchInfo parameter so that the launch function doesn't keep getting new arguments as they are needed. - TestCase::Setup() and TestCase::Launch(SBLaunchInfo) now return bool to indicate success of setup and launch. - ActionWanted::Next(SBThread) was renamed to ActionWanted::StepOver(SBThread) - ActionWanted::Finish(SBThread) was renamed to ActionWanted::StepOut(SBThread) llvm-svn: 177376
2013-03-19 12:41:22 +08:00
SBFrame frame_zero(m_thread.GetFrameAtIndex(0));
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
m_dump_nsarray_measurement(frame_zero.FindVariable("nsarray", lldb::eDynamicCanRunTarget));
m_dump_nsarray_measurement(frame_zero.FindVariable("nsmutablearray", lldb::eDynamicCanRunTarget));
m_dump_nsdictionary_measurement(frame_zero.FindVariable("nsdictionary", lldb::eDynamicCanRunTarget));
m_dump_nsdictionary_measurement(frame_zero.FindVariable("nsmutabledictionary", lldb::eDynamicCanRunTarget));
m_dump_nsstring_measurement(frame_zero.FindVariable("str0", lldb::eDynamicCanRunTarget));
m_dump_nsstring_measurement(frame_zero.FindVariable("str1", lldb::eDynamicCanRunTarget));
m_dump_nsstring_measurement(frame_zero.FindVariable("str2", lldb::eDynamicCanRunTarget));
m_dump_nsstring_measurement(frame_zero.FindVariable("str3", lldb::eDynamicCanRunTarget));
m_dump_nsstring_measurement(frame_zero.FindVariable("str4", lldb::eDynamicCanRunTarget));
m_dump_nsdate_measurement(frame_zero.FindVariable("me", lldb::eDynamicCanRunTarget));
m_dump_nsdate_measurement(frame_zero.FindVariable("cutie", lldb::eDynamicCanRunTarget));
m_dump_nsdate_measurement(frame_zero.FindVariable("mom", lldb::eDynamicCanRunTarget));
m_dump_nsdate_measurement(frame_zero.FindVariable("dad", lldb::eDynamicCanRunTarget));
m_dump_nsdate_measurement(frame_zero.FindVariable("today", lldb::eDynamicCanRunTarget));
m_dump_nsbundle_measurement(frame_zero.FindVariable("bundles", lldb::eDynamicCanRunTarget));
m_dump_nsbundle_measurement(frame_zero.FindVariable("frameworks", lldb::eDynamicCanRunTarget));
m_dump_nsset_measurement(frame_zero.FindVariable("nsset", lldb::eDynamicCanRunTarget));
m_dump_nsset_measurement(frame_zero.FindVariable("nsmutableset", lldb::eDynamicCanRunTarget));
m_dump_std_vector_measurement(frame_zero.FindVariable("vector", lldb::eDynamicCanRunTarget));
m_dump_std_list_measurement(frame_zero.FindVariable("list", lldb::eDynamicCanRunTarget));
m_dump_std_map_measurement(frame_zero.FindVariable("map", lldb::eDynamicCanRunTarget));
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 llvm-svn: 177597
2013-03-21 07:01:28 +08:00
auto sstr0 = frame_zero.FindVariable("sstr0", lldb::eDynamicCanRunTarget);
auto sstr1 = frame_zero.FindVariable("sstr1", lldb::eDynamicCanRunTarget);
auto sstr2 = frame_zero.FindVariable("sstr2", lldb::eDynamicCanRunTarget);
auto sstr3 = frame_zero.FindVariable("sstr3", lldb::eDynamicCanRunTarget);
auto sstr4 = frame_zero.FindVariable("sstr4", lldb::eDynamicCanRunTarget);
Modify code to adhere to LLDB coding conventions. llvm-svn: 177623
2013-03-21 11:32:24 +08:00
m_dump_std_string_measurement.Start();
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 llvm-svn: 177597
2013-03-21 07:01:28 +08:00
Xcode::FetchVariable(sstr0,0,false);
Modify code to adhere to LLDB coding conventions. llvm-svn: 177623
2013-03-21 11:32:24 +08:00
m_dump_std_string_measurement.Stop();
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 llvm-svn: 177597
2013-03-21 07:01:28 +08:00
Modify code to adhere to LLDB coding conventions. llvm-svn: 177623
2013-03-21 11:32:24 +08:00
m_dump_std_string_measurement.Start();
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 llvm-svn: 177597
2013-03-21 07:01:28 +08:00
Xcode::FetchVariable(sstr1,0,false);
Modify code to adhere to LLDB coding conventions. llvm-svn: 177623
2013-03-21 11:32:24 +08:00
m_dump_std_string_measurement.Stop();
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 llvm-svn: 177597
2013-03-21 07:01:28 +08:00
Modify code to adhere to LLDB coding conventions. llvm-svn: 177623
2013-03-21 11:32:24 +08:00
m_dump_std_string_measurement.Start();
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 llvm-svn: 177597
2013-03-21 07:01:28 +08:00
Xcode::FetchVariable(sstr2,0,false);
Modify code to adhere to LLDB coding conventions. llvm-svn: 177623
2013-03-21 11:32:24 +08:00
m_dump_std_string_measurement.Stop();
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 llvm-svn: 177597
2013-03-21 07:01:28 +08:00
Modify code to adhere to LLDB coding conventions. llvm-svn: 177623
2013-03-21 11:32:24 +08:00
m_dump_std_string_measurement.Start();
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 llvm-svn: 177597
2013-03-21 07:01:28 +08:00
Xcode::FetchVariable(sstr3,0,false);
Modify code to adhere to LLDB coding conventions. llvm-svn: 177623
2013-03-21 11:32:24 +08:00
m_dump_std_string_measurement.Stop();
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 llvm-svn: 177597
2013-03-21 07:01:28 +08:00
Modify code to adhere to LLDB coding conventions. llvm-svn: 177623
2013-03-21 11:32:24 +08:00
m_dump_std_string_measurement.Start();
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 llvm-svn: 177597
2013-03-21 07:01:28 +08:00
Xcode::FetchVariable(sstr4,0,false);
Modify code to adhere to LLDB coding conventions. llvm-svn: 177623
2013-03-21 11:32:24 +08:00
m_dump_std_string_measurement.Stop();
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 llvm-svn: 177597
2013-03-21 07:01:28 +08:00
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
}
Code cleanup: - don't use preprocessor macros - use switch statements - don't put anything in the lldb namespace, use "lldb_perf" namespace. - Pass the action struct into each TestStep() for each step fill in - Modify the ActionWanted class to have accessors to make the continue, next, finish, kill instead of using preproc macros llvm-svn: 177332
2013-03-19 06:34:00 +08:00
virtual void
TestStep (int counter, ActionWanted &next_action)
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
{
Code cleanup: - don't use preprocessor macros - use switch statements - don't put anything in the lldb namespace, use "lldb_perf" namespace. - Pass the action struct into each TestStep() for each step fill in - Modify the ActionWanted class to have accessors to make the continue, next, finish, kill instead of using preproc macros llvm-svn: 177332
2013-03-19 06:34:00 +08:00
switch (counter)
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
{
Code cleanup: - don't use preprocessor macros - use switch statements - don't put anything in the lldb namespace, use "lldb_perf" namespace. - Pass the action struct into each TestStep() for each step fill in - Modify the ActionWanted class to have accessors to make the continue, next, finish, kill instead of using preproc macros llvm-svn: 177332
2013-03-19 06:34:00 +08:00
case 0:
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. llvm-svn: 179246
2013-04-11 08:28:12 +08:00
m_target.BreakpointCreateByLocation("fmts_tester.mm", 78);
Code cleanup: - don't use preprocessor macros - use switch statements - don't put anything in the lldb namespace, use "lldb_perf" namespace. - Pass the action struct into each TestStep() for each step fill in - Modify the ActionWanted class to have accessors to make the continue, next, finish, kill instead of using preproc macros llvm-svn: 177332
2013-03-19 06:34:00 +08:00
next_action.Continue();
break;
case 1:
DoTest ();
next_action.Continue();
break;
case 2:
DoTest ();
next_action.Continue();
break;
case 3:
DoTest ();
next_action.Continue();
break;
case 4:
DoTest ();
next_action.Continue();
break;
case 5:
DoTest ();
next_action.Continue();
break;
case 6:
DoTest ();
next_action.Continue();
break;
case 7:
DoTest ();
next_action.Continue();
break;
case 8:
DoTest ();
next_action.Continue();
break;
case 9:
DoTest ();
next_action.Continue();
break;
case 10:
DoTest ();
next_action.Continue();
break;
default:
next_action.Kill();
break;
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
}
}
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 llvm-svn: 177696
2013-03-22 10:31:35 +08:00
virtual void
WriteResults (Results &results)
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
{
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 llvm-svn: 177696
2013-03-22 10:31:35 +08:00
m_dump_std_vector_measurement.WriteAverageValue(results);
m_dump_std_list_measurement.WriteAverageValue(results);
m_dump_std_map_measurement.WriteAverageValue(results);
m_dump_std_string_measurement.WriteAverageValue(results);
m_dump_nsstring_measurement.WriteAverageValue(results);
m_dump_nsarray_measurement.WriteAverageValue(results);
m_dump_nsdictionary_measurement.WriteAverageValue(results);
m_dump_nsset_measurement.WriteAverageValue(results);
m_dump_nsbundle_measurement.WriteAverageValue(results);
m_dump_nsdate_measurement.WriteAverageValue(results);
results.Write(m_out_path.c_str());
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
}
private:
// C++ formatters
TimeMeasurement<std::function<void(SBValue)>> m_dump_std_vector_measurement;
TimeMeasurement<std::function<void(SBValue)>> m_dump_std_list_measurement;
TimeMeasurement<std::function<void(SBValue)>> m_dump_std_map_measurement;
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 llvm-svn: 177597
2013-03-21 07:01:28 +08:00
TimeMeasurement<std::function<void()>> m_dump_std_string_measurement;
<rdar://problem/13228487> A test case for the performance of some LLDB formatters Changes and improvements to the testing infrastructure itself llvm-svn: 177100
2013-03-15 03:00:42 +08:00
// Cocoa formatters
TimeMeasurement<std::function<void(SBValue)>> m_dump_nsstring_measurement;
TimeMeasurement<std::function<void(SBValue)>> m_dump_nsarray_measurement;
TimeMeasurement<std::function<void(SBValue)>> m_dump_nsdictionary_measurement;
TimeMeasurement<std::function<void(SBValue)>> m_dump_nsset_measurement;
TimeMeasurement<std::function<void(SBValue)>> m_dump_nsbundle_measurement;
TimeMeasurement<std::function<void(SBValue)>> m_dump_nsdate_measurement;
// useful files
std::string m_app_path;
std::string m_out_path;
};
// argv[1] == path to app
// argv[2] == path to result
int main(int argc, const char * argv[])
{
FormattersTest frmtest;
frmtest.SetVerbose(true);
TestCase::Run(frmtest,argc,argv);
return 0;
}