> My understanding was that a MachineOutput.Statement.Move would always have > source and destination of the same type. Mine too. > If the C backend produces an executable, then my guess is that somewhere > along the line a coercion function got dropped, which C is adding back. > Otherwise, I'd guess that void creeped in somehow. The C backend G1 compiled fine. I'm looking into it.