[Lldb-commits] [PATCH] D37930: Use ThreadLauncher to launch TaskPool threads

2017-09-19 Thread Francis Ricci via Phabricator via lldb-commits
This revision was automatically updated to reflect the committed changes. Closed by commit rL313637: Use ThreadLauncher to launch TaskPool threads (authored by fjricci). Changed prior to commit: https://reviews.llvm.org/D37930?vs=115691&id=115844#toc Repository: rL LLVM https://reviews.llvm

[Lldb-commits] [PATCH] D37930: Use ThreadLauncher to launch TaskPool threads

2017-09-19 Thread Tamas Berghammer via Phabricator via lldb-commits
tberghammer accepted this revision. tberghammer added a comment. This revision is now accepted and ready to land. I don't really have an opinion if moving TaskPool to Host is a good or bad idea (haven't followed the recent layering efforts) but other then that looks good. I also tested it on Lin

[Lldb-commits] [PATCH] D37930: Use ThreadLauncher to launch TaskPool threads

2017-09-18 Thread Francis Ricci via Phabricator via lldb-commits
fjricci updated this revision to Diff 115691. fjricci added a comment. Herald added subscribers: JDevlieghere, mgorny. Move TaskPool from Utility to Host https://reviews.llvm.org/D37930 Files: include/lldb/Host/TaskPool.h include/lldb/Utility/TaskPool.h lldb.xcodeproj/project.pbxproj so

Re: [Lldb-commits] [PATCH] D37930: Use ThreadLauncher to launch TaskPool threads

2017-09-18 Thread Tamas Berghammer via lldb-commits
Are you building with cmake or with XCode? If you are using cmake then you should be able to reproduce it with running "ninja check-lldb-unit". It failed to link one of the unittest targets because UtilityTests don't have an explicit dependency on lldbHost (where ThreadLauncher is defined). You can

[Lldb-commits] [PATCH] D37930: Use ThreadLauncher to launch TaskPool threads

2017-09-18 Thread Francis Ricci via Phabricator via lldb-commits
fjricci reopened this revision. fjricci added a comment. This revision is now accepted and ready to land. Is ThreadLauncher unavailable in this code for some reason? The link failed on linux buildbots (building lldb on Darwin was fine locally): http://lab.llvm.org:8011/builders/lldb-x86_64-ubunt

[Lldb-commits] [PATCH] D37930: Use ThreadLauncher to launch TaskPool threads

2017-09-18 Thread Francis Ricci via Phabricator via lldb-commits
This revision was automatically updated to reflect the committed changes. Closed by commit rL313537: Use ThreadLauncher to launch TaskPool threads (authored by fjricci). Changed prior to commit: https://reviews.llvm.org/D37930?vs=115484&id=115658#toc Repository: rL LLVM https://reviews.llvm

[Lldb-commits] [PATCH] D37930: Use ThreadLauncher to launch TaskPool threads

2017-09-18 Thread Tamas Berghammer via Phabricator via lldb-commits
tberghammer accepted this revision. tberghammer added a comment. Looks good Comment at: source/Utility/TaskPool.cpp:61 +lldb_private::ThreadLauncher::LaunchThread("task-pool.worker", WorkerPtr, + this, nullptr, 8 * 1024 * 1024)

[Lldb-commits] [PATCH] D37930: Use ThreadLauncher to launch TaskPool threads

2017-09-15 Thread Francis Ricci via Phabricator via lldb-commits
fjricci created this revision. This allows for the stack size to be configured, which isn't possible with std::thread. Prevents overflowing the stack when performing complex operations in the task pool on darwin, where the default pthread stack size is only 512kb. https://reviews.llvm.org/D37930