diff options
| author | Roman Lebedev <lebedev.ri@gmail.com> | 2021-07-09 13:36:21 +0300 |
|---|---|---|
| committer | Roman Lebedev <lebedev.ri@gmail.com> | 2021-07-09 14:16:54 +0300 |
| commit | 52aeacfbf5ce5f949efe0eae029e56db171ea1f7 (patch) | |
| tree | 3f3b75913f9468c47abd61c04d2cd67a9a1dd1de /llvm/lib/CodeGen/MachineFunction.cpp | |
| parent | 329f8197ef59f9bd23328b52d623ba768b51dbb2 (diff) | |
| download | llvm-52aeacfbf5ce5f949efe0eae029e56db171ea1f7.zip llvm-52aeacfbf5ce5f949efe0eae029e56db171ea1f7.tar.gz llvm-52aeacfbf5ce5f949efe0eae029e56db171ea1f7.tar.bz2 | |
Revert "Temporarily do not drop volatile stores before unreachable"
This reverts commit 4e413e16216d0c94ada2171f3c59e0a85f4fa4b6,
which landed almost 10 months ago under premise that the original behavior
didn't match reality and was breaking users, even though it was correct as per
the LangRef. But the LangRef change still hasn't appeared, which might suggest
that the affected parties aren't really worried about this problem.
Please refer to discussion in:
* https://reviews.llvm.org/D87399 (`Revert "[InstCombine] erase instructions leading up to unreachable"`)
* https://reviews.llvm.org/D53184 (`[LangRef] Clarify semantics of volatile operations.`)
* https://reviews.llvm.org/D87149 (`[InstCombine] erase instructions leading up to unreachable`)
clang has `-Wnull-dereference` which will diagnose the obvious cases
of null dereference, it was adjusted in f4877c78c0fc98be47b926439bbfe33d5e1d1b6d,
but it will only catch the cases where the pointer is a null literal,
it will not catch the cases where an arbitrary store is expected to trap.
Differential Revision: https://reviews.llvm.org/D105338
Diffstat (limited to 'llvm/lib/CodeGen/MachineFunction.cpp')
0 files changed, 0 insertions, 0 deletions