X21, X29, X13 // z_lo[1] = x[1] * y + z[1] + c SLTU X21, X13, X22 ADD X12, X22, X29 // next c MULHU X14, X6, X15 // z_hi[2] = x[2] * y MUL X14, X6, X14 // z_lo[2] = x[2] * y ADD X14, X16, X21 // z_lo[2] = x[2] * y + z[2] SLTU X14, X21, X22 ADD X15, X22, X15 // z_hi[2] = x[2] * y + z[2] ADD X21, X29, X16 // z_lo[2] = x[2] * y + z[2] + c SLTU X21, X16, X22 ADD X15, X22, X29 // next c MULHU X17, X6, X18 // z_hi[3] = x[3] * y MUL X17, X6, X17 // z_lo[3] = x[3] * y ADD X17, X19, X21 // z_lo[3] = x[3] * y...

For assembly functions with Go prototypes, <code>go</code> <code>vet</code> will check that the argument names
and offsets match.
On 32-bit systems, the low and high 32 bits of a 64-bit value are distinguished by adding
a <code>_lo</code> or <code>_hi</code> suffix to the name, as in <code>arg_lo+0(FP)</code> or <code>arg_hi+4(FP)</code>.
If a Go prototype does not name its result, the expected assembly name is <code>ret</code>.
</p>

<p>