[ValueTracking] Move GlobalAlias handling to be after the max depth check in computeK...
authorMichael Kuperstein <michael.m.kuperstein@intel.com>
Tue, 23 Dec 2014 11:33:41 +0000 (11:33 +0000)
committerMichael Kuperstein <michael.m.kuperstein@intel.com>
Tue, 23 Dec 2014 11:33:41 +0000 (11:33 +0000)
GlobalAlias handling used to be after GlobalValue handling, which meant it was, in practice, dead code. r220165 moved GlobalAlias handling to be before GlobalValue handling, but also moved it to be before the max depth check, causing an assert due to a recursion depth limit violation.

This moves GlobalAlias handling forward to where it's safe, and changes the GlobalValue handling to only look at GlobalObjects.

Differential Revision: http://reviews.llvm.org/D6758

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


No differences found