When we are emitting a `Move` from a Tmp to a named-register Tmp that matches
its current allocation, we currently generate code that spills the source tmp to
the stack, allocates a new (distinct) register for it, restores it there, and
then moves it; this seems wasteful and, although this kind of situation in Air
is not common on x86_64, we do generate it on 32-bit ARM targets