diff options
| author | Eli Friedman <efriedma@codeaurora.org> | 2019-01-22 00:42:20 +0000 |
|---|---|---|
| committer | Eli Friedman <efriedma@codeaurora.org> | 2019-01-22 00:42:20 +0000 |
| commit | 9ba168204bb4e36aebad4869b45b68a77b7dd4e3 (patch) | |
| tree | 51fde9897f1f42caa1ce7abcf03b848432a4ab3f /llvm/lib/Bitcode/Reader/BitcodeReader.cpp | |
| parent | b793d25443d0322e32d690762d5885ec79496695 (diff) | |
| download | bcm5719-llvm-9ba168204bb4e36aebad4869b45b68a77b7dd4e3.tar.gz bcm5719-llvm-9ba168204bb4e36aebad4869b45b68a77b7dd4e3.zip | |
[LangRef] Clarify semantics of volatile operations.
Specifically, clarify the following:
1. Volatile load and store may access addresses that are not memory.
2. Volatile load and store do not modify arbitrary memory.
3. Volatile load and store do not trap.
Prompted by recent volatile discussion on llvmdev.
Currently, there's sort of a split in the source code about whether
volatile operations are allowed to trap; this resolves that dispute in
favor of not allowing them to trap.
Differential Revision: https://reviews.llvm.org/D53184
llvm-svn: 351772
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions
