summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/help/TestHelp.py
diff options
context:
space:
mode:
authorVedant Kumar <vsk@apple.com>2016-10-19 17:55:44 +0000
committerVedant Kumar <vsk@apple.com>2016-10-19 17:55:44 +0000
commit6fd94bf47c9d43ae159f775f483b91ad8b995ffb (patch)
tree21fdb24105da4fcf1510e16cb800c0a1a1257c0e /lldb/packages/Python/lldbsuite/test/help/TestHelp.py
parent1f90f2d33f72ec9e34da496323c1ccff89b23c21 (diff)
downloadbcm5719-llvm-6fd94bf47c9d43ae159f775f483b91ad8b995ffb.tar.gz
bcm5719-llvm-6fd94bf47c9d43ae159f775f483b91ad8b995ffb.zip
[llvm-cov] Don't spawn a thread unless ThreadCount > 1
Initializing a ThreadPool with ThreadCount = 1 spawns a thread even though we don't need to. This is at least slower than it needs to be, and at worst may somehow be exacerbating PR30735 (llvm-cov times out on ARM bots). As a follow-up, I'll try to add logic to llvm::ThreadPool to avoid spawning a thread when ThreadCount = 1. llvm-svn: 284621
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/help/TestHelp.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud