findReachingDefs was incorrectly using its fast path of just blitting in
the live range extension when it did not see an undef itself but
encountered an undef live out of a predecessor block.
Now RegisterCoalescing calls extendToIndices (D49097), the bug was
causing an incorrect subrange which led to a "Couldn't join subrange!"
assert in a later coalesce.
Change-Id: I01c942b41ab5a145348289c8b221c45a2ec7200f
Could you check that the coalescing does the right thing instead of just checking that we emit a function?