From 524686738460d61df0cb46d1398fffa9734f1378 Mon Sep 17 00:00:00 2001 From: Ahmed Bougacha Date: Fri, 11 Sep 2015 17:08:28 +0000 Subject: [CodeGen] Refactor TLI/AtomicExpand interface to make LLSC explicit. We used to have this magic "hasLoadLinkedStoreConditional()" callback, which really meant two things: - expand cmpxchg (to ll/sc). - expand atomic loads using ll/sc (rather than cmpxchg). Remove it, and, instead, introduce explicit callbacks: - bool shouldExpandAtomicCmpXchgInIR(inst) - AtomicExpansionKind shouldExpandAtomicLoadInIR(inst) Differential Revision: http://reviews.llvm.org/D12557 llvm-svn: 247429 --- llvm/docs/Atomics.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'llvm/docs/Atomics.rst') diff --git a/llvm/docs/Atomics.rst b/llvm/docs/Atomics.rst index 9068df46b02..79ab74792dd 100644 --- a/llvm/docs/Atomics.rst +++ b/llvm/docs/Atomics.rst @@ -446,7 +446,7 @@ It is often easiest for backends to use AtomicExpandPass to lower some of the atomic constructs. Here are some lowerings it can do: * cmpxchg -> loop with load-linked/store-conditional - by overriding ``hasLoadLinkedStoreConditional()``, ``emitLoadLinked()``, + by overriding ``shouldExpandAtomicCmpXchgInIR()``, ``emitLoadLinked()``, ``emitStoreConditional()`` * large loads/stores -> ll-sc/cmpxchg by overriding ``shouldExpandAtomicStoreInIR()``/``shouldExpandAtomicLoadInIR()`` -- cgit v1.2.3