We're currently running into:
...
FAIL: gdb.trace/entry-values.exp: disassemble bar
...
Since commit
36938cabf0 "x86: avoid attaching suffixes to unambiguous insns",
"callq" is disassembled as "call", and the test-case expects "callq".
Fix this by expecting "call" instead.
Tested on x86_64-linux.
gdb/testsuite/ChangeLog:
2020-07-15 Tom de Vries <tdevries@suse.de>
* gdb.trace/entry-values.exp: Expect "call" instead of "callq" if
is_amd64_regs_target.
+2020-07-15 Tom de Vries <tdevries@suse.de>
+
+ * gdb.trace/entry-values.exp: Expect "call" instead of "callq" if
+ is_amd64_regs_target.
+
2020-07-15 Andrew Burgess <andrew.burgess@embecosm.com>
* gdb.fortran/ptype-on-functions.exp: Add more tests.
# returns. The only exception is JALRC, in which case execution
# resumes from `insn1' instead.
set call_insn {jalrc|[jb]al[sxr]*[ \t][^\r\n]+\r\n}
-} elseif [is_amd64_regs_target] {
- set call_insn "callq"
} else {
set call_insn "call"
}