From 38bf51134d1a58f155c89f2b1c7bf885c2604ead Mon Sep 17 00:00:00 2001 From: Jan Beulich Date: Thu, 23 Nov 2017 10:57:54 +0100 Subject: x86/Intel: don't report multiple errors for a single insn operand Multiple errors are more confusing than helpful, as the more generic one often implies a sufficiently different adjustment than would actually be needed to fix the code. Additionally it makes it more cumbersome to add missing error checks, as the testsuite then needs extra updating. --- gas/config/tc-i386-intel.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'gas/config') diff --git a/gas/config/tc-i386-intel.c b/gas/config/tc-i386-intel.c index b8874e4..79fe0b4 100644 --- a/gas/config/tc-i386-intel.c +++ b/gas/config/tc-i386-intel.c @@ -580,12 +580,14 @@ i386_intel_operand (char *operand_string, int got_a_float) if (!is_end_of_line[(unsigned char) *input_line_pointer]) { - as_bad (_("junk `%s' after expression"), input_line_pointer); + if (ret) + as_bad (_("junk `%s' after expression"), input_line_pointer); ret = 0; } else if (exp.X_op == O_illegal || exp.X_op == O_absent) { - as_bad (_("invalid expression")); + if (ret) + as_bad (_("invalid expression")); ret = 0; } else if (!intel_state.has_offset -- cgit v1.1