summaryrefslogtreecommitdiff
path: root/lib/Target/X86
diff options
context:
space:
mode:
authorZachary Turner <zturner@google.com>2014-06-17 21:54:18 +0000
committerZachary Turner <zturner@google.com>2014-06-17 21:54:18 +0000
commit97a66e604970685e7c7c954d3fb9ab6dab2c6f8e (patch)
tree051a9ece43ef671700a01b131b60456318c9d467 /lib/Target/X86
parent540fe7f20ee5a718abd2d5f1fff5092485a1dbc6 (diff)
downloadllvm-97a66e604970685e7c7c954d3fb9ab6dab2c6f8e.tar.gz
llvm-97a66e604970685e7c7c954d3fb9ab6dab2c6f8e.tar.bz2
llvm-97a66e604970685e7c7c954d3fb9ab6dab2c6f8e.tar.xz
Remove more occurrences of the unused-mutex-parameter pattern.
This pattern loses some of its usefulness when the mutex type is statically polymorphic as opposed to runtime polymorphic, as swapping out the mutex type requires changing a significant number of function parameters, and templatizing the function parameter requires the methods to be defined in the headers. Furthermore, if LLVM is compiled with threads disabled then there may even be no mutex to acquire anyway, so it should not be up to individual APIs to know whether or not acquiring a mutex is required to use those APIs to begin with. It should be up to the user of the API. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@211125 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/Target/X86')
0 files changed, 0 insertions, 0 deletions