[PATCH] D20776: [CFLAA] Teach cfl-aa to understand heap memory allocation

[Jia Chen via llvm-commits]

grievejia added a comment.

In http://reviews.llvm.org/D20776#443674, @dberlin wrote:

> This is because while it introduces no aliases itself, it does introduce a
>  variable that can be aliased.
>  If that variable is reached through other mechanisms, it may be an alias :)


I agree.

> If you say they do *nothing*, as you've done here, nothing will ever alias

>  the result of malloc, even something that *should*.

> 

> Am i missing something?


"Nothing" is currently what happens to AllocaInsts. I just tried to be consistent with how AllocaInst is treated.

Also, "nothing" only applies to the malloc() inst/AllocaInst itself. If any other instructions use it, the allocated value should get linked to other part of the function.


http://reviews.llvm.org/D20776