This makes the C11 / C++11 *ABI* atomic ordering accessible from LLVM, as discussed in http://reviews.llvm.org/D18200#inline-151433
Details
Details
Diff Detail
Diff Detail
Event Timeline
include/llvm/Support/AtomicOrdering.h | ||
---|---|---|
24–35 | Why does LLVM need to know about these? It seems like they're specific to the frontend. Is there some way in which they're not? (Is some upcoming change going to use these from LLVM?) What happens if some C ABI picks different values? |
include/llvm/Support/AtomicOrdering.h | ||
---|---|---|
24–35 | See this patch by @jyknight: http://reviews.llvm.org/D18200#inline-151433 |
Comment Actions
Please replace the function libcallAtomicModel in AtomicExpandPass.cpp with your new toCABI. Other than that, LGTM.
Why does LLVM need to know about these? It seems like they're specific to the frontend. Is there some way in which they're not? (Is some upcoming change going to use these from LLVM?)
What happens if some C ABI picks different values?