forked from OSchip/llvm-project
6569cf2a44
This revision refactors the usage of multithreaded utilities in MLIR to use a common thread pool within the MLIR context, in addition to a new utility that makes writing multi-threaded code in MLIR less error prone. Using a unified thread pool brings about several advantages: * Better thread usage and more control We currently use the static llvm threading utilities, which do not allow multiple levels of asynchronous scheduling (even if there are open threads). This is due to how the current TaskGroup structure works, which only allows one truly multithreaded instance at a time. By having our own ThreadPool we gain more control and flexibility over our job/thread scheduling, and in a followup can enable threading more parts of the compiler. * The static nature of TaskGroup causes issues in certain configurations Due to the static nature of TaskGroup, there have been quite a few problems related to destruction that have caused several downstream projects to disable threading. See D104207 for discussion on some related fallout. By having a ThreadPool scoped to the context, we don't have to worry about destruction and can ensure that any additional MLIR thread usage ends when the context is destroyed. Differential Revision: https://reviews.llvm.org/D104516 |
||
|---|---|---|
| .. | ||
| crash-recovery.mlir | ||
| dynamic-pipeline-fail-on-parent.mlir | ||
| dynamic-pipeline-nested.mlir | ||
| dynamic-pipeline.mlir | ||
| invalid-pass.mlir | ||
| ir-printing.mlir | ||
| pass-timing.mlir | ||
| pipeline-options-parsing.mlir | ||
| pipeline-parsing.mlir | ||
| pipeline-stats.mlir | ||
| run-reproducer.mlir | ||