[all-commits] [llvm/llvm-project] 5c486c: [LLVM IR] Allow volatile stores to trap.

[Eli Friedman via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 5c486ce04db4d33ae5be65dac4a03d1b0f46f3e2
      https://github.com/llvm/llvm-project/commit/5c486ce04db4d33ae5be65dac4a03d1b0f46f3e2
  Author: Eli Friedman <efriedma at quicinc.com>
  Date:   2021-07-26 (Mon, 26 Jul 2021)

  Changed paths:
    M llvm/docs/LangRef.rst
    M llvm/lib/Analysis/ValueTracking.cpp
    M llvm/lib/IR/Instruction.cpp
    M llvm/lib/Transforms/InstCombine/InstructionCombining.cpp
    M llvm/lib/Transforms/Utils/SimplifyCFG.cpp
    M llvm/test/Transforms/FunctionAttrs/nosync.ll
    M llvm/test/Transforms/LICM/sink-debuginfo-preserve.ll
    M llvm/test/Transforms/PhaseOrdering/inlining-alignment-assumptions.ll

  Log Message:
  -----------
  [LLVM IR] Allow volatile stores to trap.

Proposed alternative to D105338.

This is ugly, but short-term I think it's the best way forward: first,
let's formalize the hacks into a coherent model. Then we can consider
extensions of that model (we could have different flavors of volatile
with different rules).

Differential Revision: https://reviews.llvm.org/D106309