Fix a latent bug in the asm code. I think that technically, using "*m0" instead of "*0" allows LLVM to pick between using the same memory as output 0 and using a new memory location. (So far I haven't been able to construct a testcase that actually breaks because of this, though)

module complex5;

void main()
{
    cfloat c = 3+2i;
    foo(c);
}

void foo(cfloat c)
{
    assert(c.re > 2.9999  && c.re < 3.0001);
    assert(c.im > 1.9999i && c.im < 2.0001i);
}