summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallStopAndContinue.py
diff options
context:
space:
mode:
authorRafael Espindola <rafael.espindola@gmail.com>2017-10-04 20:27:01 +0000
committerRafael Espindola <rafael.espindola@gmail.com>2017-10-04 20:27:01 +0000
commit8c0ff9508da5f02e8ce6580a126a2018c9bf702a (patch)
tree684e2b65a792c355a8c8659a94b735e82237976d /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallStopAndContinue.py
parent4c33d5213b91b367a8392c19b4a110f62243a91d (diff)
downloadbcm5719-llvm-8c0ff9508da5f02e8ce6580a126a2018c9bf702a.tar.gz
bcm5719-llvm-8c0ff9508da5f02e8ce6580a126a2018c9bf702a.zip
Bring r314809 back.
But now include a check for CPU_COUNT so we still build on 10 year old versions of glibc. Original message: Use sched_getaffinity instead of std::thread::hardware_concurrency. The issue with std::thread::hardware_concurrency is that it forwards to libc and some implementations (like glibc) don't take thread affinity into consideration. With this change a llvm program that can execute in only 2 cores will use 2 threads, even if the machine has 32 cores. This makes benchmarking a lot easier, but should also help if someone doesn't want to use all cores for compilation for example. llvm-svn: 314931
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallStopAndContinue.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud