LLVM with the emscripten fastcomp javascript backend https://git.amat.us/emscripten-fastcomp/atom/test/Transforms/JumpThreading/phi-eq.ll?h=1.13.0 2012-05-10T16:55:31Z 2012-05-10T16:55:31Z Joel Jones joel_k_jones@apple.com 2012-05-10T16:55:31Z urn:sha1:9777f61bfe36a53757977cd777f2b4e73fc3e8a3 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@156551 91177308-0d34-0410-b5e6-96231b3b80d8 2012-05-10T15:59:41Z Joel Jones joel_k_jones@apple.com 2012-05-10T15:59:41Z urn:sha1:9df72a93ef27a27c6853eed3ed92c9e0b62c9ca6 Instruction::IsIdenticalToWhenDefined. This manifested itself when inlining two calls to the same function. The inlined function had a switch statement that returned one of a set of global variables. Without this modification, the two phi instructions that chose values from the branches of the switch instruction inlined from the callee were considered equivalent and jump-threading replaced a load for the first switch value with a phi selecting from the second switch, thereby producing incorrect code. This patch has been tested with "make check-all", "lnt runteste nt", and llvm self-hosted, and on the original program that had this problem, wireshark. <rdar://problem/11025519> git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@156548 91177308-0d34-0410-b5e6-96231b3b80d8