Jan Beulich 65fca0597f x86: replace adhoc (partly wrong) ambiguous operand checking for MOVSX/MOVZX ... For these to get treatment consistent with other operand size checking the special logic shouldn't live in md_assemble(), but process_suffix(). And there's more logic involved than simply zapping the suffix. Note however that MOVS[BW]* and MOVZ[BW]* still won't be fully consistent, due to the objection to fold MOVS* templates just like was done for MOVZ* in c07315e0c6 ("x86: allow suffix-less movzw and 64-bit movzb"). Note further that it is against my own intentions to have MOVSX/MOVZX silently default to a byte source in AT&T mode. This should happen only when the destination register is a 16-bit one. In all other cases there is an ambiguity, and the user should be warned. But it was explicitly requested for this to be done in a way inconsistent with everything else. Note finally that the assembler change points out (and this patch fixes) a wrong Intel syntax test introduced by bc31405ebb ("x86-64: Properly encode and decode movsxd"): When source code specifies a 16-bit destination register, disassembly expectations shouldn't have been to find a 32-bit one.		2020-02-14 14:27:28 +01:00
..
config	Update year range in copyright notice of binutils files	2020-01-01 18:42:54 +10:30
gas	x86: replace adhoc (partly wrong) ambiguous operand checking for MOVSX/MOVZX	2020-02-14 14:27:28 +01:00
lib	Replace deprecated tcl case statements with switch statements	2020-01-27 22:52:15 +10:30
ChangeLog-2004
ChangeLog-2005
ChangeLog-2006
ChangeLog-2007
ChangeLog-2008
ChangeLog-2009
ChangeLog-2010
ChangeLog-2011
ChangeLog-2012
ChangeLog-2013
ChangeLog-2014	ChangeLog rotatation and copyright year update	2015-01-02 00:53:45 +10:30
ChangeLog-2015	binutils ChangeLog rotation	2016-01-01 22:59:17 +10:30
ChangeLog-9303