aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
diff options
context:
space:
mode:
authorPhilip Reames <listmail@philipreames.com>2016-05-06 22:17:01 +0000
committerPhilip Reames <listmail@philipreames.com>2016-05-06 22:17:01 +0000
commit6f4d0088c6d756d0be94e6c807deb56c7ce36b9c (patch)
tree24f677fc31e6ebb96196e08d305c3e7e391b93ea /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
parent5a1b5ef9ebe76f50197c1180c894d8ba6f62e04d (diff)
downloadllvm-6f4d0088c6d756d0be94e6c807deb56c7ce36b9c.zip
llvm-6f4d0088c6d756d0be94e6c807deb56c7ce36b9c.tar.gz
llvm-6f4d0088c6d756d0be94e6c807deb56c7ce36b9c.tar.bz2
Reapply 267210 with fix for PR27490
Original Commit Message Extend load/store type canonicalization to handle unordered operations Extend the type canonicalization logic to work for unordered atomic loads and stores. Note that while this change itself is fairly simple and low risk, there's a reasonable chance this will expose problems in the backends by suddenly generating IR they wouldn't have seen before. Anything of this nature will be an existing bug in the backend (you could write an atomic float load), but this will definitely change the frequency with which such cases are encountered. If you see problems, feel free to revert this change, but please make sure you collect a test case. Note that the concern about lowering is now much less likely. PR27490 proved that we already *were* mucking with the types of ordered atomics and volatiles. As a result, this change doesn't introduce as much new behavior as originally thought. llvm-svn: 268809
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions