The code that triggers the warning begins here:

	if kind != 0 && kind != vk {

Although the sizes are the same, the value types are different (scalar vs array). In general it is a good thing to issue a warning when there is a type clash (for example, if a param is moved into a floating point register with an FP move, but the param in question is not floating point).

Thank you Than. I know what I am doing here, so I'd like to suppress the warning somehow. I believe there are two possibilities:

1. There's an assembler syntax I am unaware of that would do what I want without triggering a vet warning. In this case please share it and resolve the issue as invalid, or:

2. Switch the register from FP to SP, as I currently do:
   MOVQ v+16(SP), AX // Mute the "invalid MOVQ of v+8(FP); vm.vmref is 8-byte value" go vet false positive.

Unfortunately, there's no elegant mapping between SP and FP, so the offsets are different, in my case by 8: 16(SP) vs. 8(FP). Pushing a programmer to write like that does more harm than vet is trying to avoid, so I'd appreciate some way of reassuring vet that the size is all that matters.

What I have seen in the past for similar problems is that folks will emit the assembly with BYTE, then include a comment explaining why and what it is. E.g.

// The following instruction below emitted as bytes to
// disable vet check, see issue #55936.
/* MOVQ    a+0(FP), AX */ BYTE $48; BYTE $8b; BYTE $44; BYTE $24; BYTE $08