Christy Lee 3cc0e935c4 Pointer types were treated as zero-size by MergeICmps ... Summary: The visitICmp analysis function would record compares of pointer types, as size 0. This causes the resulting memcmp() call to have the wrong total size. Found with "self-build" of clang/LLVM on Windows. Reviewers: christylee, trentxintong, courbet Reviewed By: courbet Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D53536 llvm-svn: 345413		2018-10-26 18:02:06 +00:00
..
alias-merge-blocks.ll	Re-submitting changes in D51550 because it failed to patch.	2018-09-24 20:47:12 +00:00
atomic.ll	Do not optimize atomic load to non-atomic memcmp	2018-09-18 17:02:42 +00:00
entry-block-shuffled.ll	[MergeICmp] Fix a bug in entry block shuffled to middle of the chain	2018-03-20 11:57:54 +00:00
int64-and-ptr.ll	Pointer types were treated as zero-size by MergeICmps	2018-10-26 18:02:06 +00:00
last-block-produce-no-value.ll	[MergeICmp] Fix a bug in MergeICmp that can lead to a block being processed more than once.	2018-02-28 12:08:00 +00:00
lit.local.cfg	…
multiple-blocks-does-work.ll	[MergeICmp] We can discard initial blocks that do other work	2018-03-05 13:54:47 +00:00
pair-int32-int32.ll	[MergeICmps] Don't crash when memcmp is not available	2018-05-19 12:51:59 +00:00
pr36557.ll	[MergeICmps] Make sure that the comparison only has one use.	2018-03-13 07:05:55 +00:00
split-block-does-work.ll	[MergeICmp] Split blocks that do other work.	2018-04-09 13:14:06 +00:00
tuple-four-int8.ll	[MergeICmp] Split blocks that do other work.	2018-04-09 13:14:06 +00:00
two-complex-bb.ll	…
volatile.ll	…