aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Reader/BitcodeReader.cpp
diff options
context:
space:
mode:
authorNikita Popov <nikita.ppv@gmail.com>2021-05-17 23:37:14 +0200
committerNikita Popov <nikita.ppv@gmail.com>2021-05-18 20:26:01 +0200
commite81334a75401f3af3b10f64e307d705d97637a03 (patch)
treebd20735b59063dcc55f64fa7d53507b03b698055 /llvm/lib/Bitcode/Reader/BitcodeReader.cpp
parent5e1421b22f642a6b34690d0d724e691ba3984836 (diff)
downloadllvm-e81334a75401f3af3b10f64e307d705d97637a03.zip
llvm-e81334a75401f3af3b10f64e307d705d97637a03.tar.gz
llvm-e81334a75401f3af3b10f64e307d705d97637a03.tar.bz2
[LICM] Remove MaybePromotable set (PR50367)
The MaybePromotable set keeps track of loads/stores for which promotion was not attempted yet. Normally, any load/stores that are promoted in the current iteration will be removed from this set, because they naturally MustAlias with the promoted value. However, if the source program has UB with metadata claiming that a store is NoAlias, while it is actually MustAlias, and multiple different pointers are promoted in the same iteration, it can happen that a store is removed that is still in the MaybePromotable set, causing a use-after-free. While this could be fixed by explicitly invalidating values in MaybePromotable in the LoopPromoter, I'm going with the more radical option of dropping the set entirely here and check all load/stores on each promotion iteration. As promotion, and especially repeated promotion, are quite rare, this doesn't seem to have any impact on compile-time. Fixes https://bugs.llvm.org/show_bug.cgi?id=50367.
Diffstat (limited to 'llvm/lib/Bitcode/Reader/BitcodeReader.cpp')
0 files changed, 0 insertions, 0 deletions