Duncan Sands b01bbdcc1a I don't see any point in having both eh.selector.i32 and eh.selector.i64, ... so get rid of eh.selector.i64 and rename eh.selector.i32 to eh.selector. Likewise for eh.typeid.for. This aligns us with gcc, which always uses a 32 bit value for the selector on all platforms. My understanding is that the register allocator used to assert if the selector intrinsic size didn't match the pointer size, and this was the reason for introducing the two variants. However my testing shows that this is no longer the case (I fixed some bugs in selector lowering yesterday, and some more today in the fastisel path; these might have caused the original problems). git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@84106 91177308-0d34-0410-b5e6-96231b3b80d8		2009-10-14 16:11:37 +00:00
..
llvm	I don't see any point in having both eh.selector.i32 and eh.selector.i64,	2009-10-14 16:11:37 +00:00
llvm-c