1
0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-11-24 03:33:20 +01:00
llvm-mirror/test/Analysis/ValueTracking
Danila Kutenin cc8987f5b5 [ValueTracking] Pointer is known nonnull after load/store
If the pointer was loaded/stored before the null check, the check
is redundant and can be removed. For now the optimizers do not
remove the nullptr check, see https://gcc.godbolt.org/z/H2r5GG.
The patch allows to use more nonnull constraints. Also, it found
one more optimization in some PowerPC test. This is my first llvm
review, I am free to any comments.

Differential Revision: https://reviews.llvm.org/D71177
2019-12-11 20:32:29 +01:00
..
aarch64.irg.ll
assume.ll
deref-bitcast-of-gep.ll
dereferenceable-and-aligned.ll
func-ptr-lsb.ll
gep-negative-issue.ll
get-pointer-base-with-const-off.ll
invariant.group.ll
known-bits-from-range-md.ll
known-non-equal.ll
known-nonnull-at.ll [ValueTracking] Pointer is known nonnull after load/store 2019-12-11 20:32:29 +01:00
known-power-of-two.ll
known-signbit-shift.ll
knownnonzero-shift.ll
knownzero-addrspacecast.ll
knownzero-shift.ll
memory-dereferenceable.ll
monotonic-phi.ll
non-negative-phi-bits.ll
numsignbits-from-assume.ll
pr23011.ll
select-pattern.ll
signbits-extract-elt.ll