Ah, that's true.  I'm still basically assuming it won't happen in practice (or very rarely.)

Another possible optimization is avoiding the memory read/write by combining vpfxs/t/d with the next instruction.  In practice in LBP, I'm only seeing a single one right before a vmov, vdot, etc.

-[Unknown]