Mikael Holmen e7f98a969c [Lint] Don't warn about noalias argument aliasing if other argument is byval ...

Summary:
When using byval, the data is effectively copied as part of the call
anyway, so we aren't actually passing the pointer and thus there is no
reason to issue a warning.

Reviewers: rnk

Reviewed By: rnk

Subscribers: llvm-commits

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

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@321478 91177308-0d34-0410-b5e6-96231b3b80d8

2017-12-27 08:48:33 +00:00

..

address-spaces.ll

Teach lint about address spaces

2014-03-06 17:33:55 +00:00

check-zero-divide.ll

…

cppeh-catch-intrinsics-clean.ll

Move the personality function from LandingPadInst to Function

2015-06-17 20:52:32 +00:00

lit.local.cfg

…

noalias-byval.ll

[Lint] Don't warn about noalias argument aliasing if other argument is byval

2017-12-27 08:48:33 +00:00

noop-cast-expr-no-pointer.ll

[Lint] Avoid failed assertion by fetching the proper pointer type

2017-10-03 06:03:49 +00:00

tail-call-byval.ll

[Lint] Don't warn about passing alloca'd value to tail call if using byval

2017-11-15 07:46:48 +00:00