D152276 wasn't handling the case where the inserted element is implicity truncated into the vector - resulting in a i1 element (implictly truncated from i8) overwriting 8 bits instead of 1 bit.
This patch is intended to be merged into 17.x so I've just disallowed any vector element vs inserted element type mismatch - technically we could be more elegant and permit truncated stores (as long as the store is still byte sized), but the use cases for that are so limited I'd prefer to play it safe for now.
Candidate patch for #64655 17.x merge
EltVT is the scalar type being inserted, but operand 0 is the vector being inserted into, so these types can never be equal. Maybe EltVT != Value.getOperand(0).getValueType().getVectorElementType()?