On Mon, Mar 23, 2026 at 7:15 AM Matheus Tavares Bernardino < matheus.bernardino@oss.qualcomm.com> wrote: > The following encodings have become stricter since v68: > > - V6_vunpackob, V6_vunpackoh: ---00 -> --000 > - V6_vaddbq/hq/wq, V6_vaddbnq/hnq/wnq: ---01 -> --001 > - V6_vsubbq/hq, V6_vsubwq/bnq/hnq/wnq: ---01/---10 -> --001/--010 > - V6_vhist, V6_vwhist128/256, V6_vwhist128/256_sat: ---00 -> --000 > - V6_vhistq, V6_vwhist128/256q, V6_vwhist128/256q_sat: ---10 -> --010 > > Pre v68 compilers, by default, already use "0" for the non-specified bit > that changed in v68, so unless someone is manually writing the binary > encoding, this should not cause any backwards incompatibility with > pre-v68 binaries. > > Signed-off-by: Matheus Tavares Bernardino < > matheus.bernardino@oss.qualcomm.com> > --- > target/hexagon/imported/mmvec/encode_ext.def | 48 ++++++++++---------- > 1 file changed, 24 insertions(+), 24 deletions(-) > Reviewed-by: Taylor Simpson