mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2024-12-27 04:52:05 +08:00
36938cabf0
"Unambiguous" is is in particular taking as reference the assembler, which also accepts certain insns - despite them allowing for varying operand size, and hence in principle being ambiguous - without any suffix. For example, from the very beginning of the life of x86-64 I had trouble understanding why a plain and simple RET had to be printed as RETQ. In case someone really used the 16-bit form, RETW disambiguates the two quite fine.
16 lines
390 B
Plaintext
16 lines
390 B
Plaintext
#objdump: -dwrj.text
|
|
#target: x86_64-*-*
|
|
|
|
.*: +file format elf.*-x86-64.*
|
|
|
|
Disassembly of section .text:
|
|
|
|
#...
|
|
[0-9a-f]+ <get_func>:
|
|
+[a-f0-9]+: 48 8b 05 ([0-9a-f]{2} ){4}[ ]+mov 0x[0-9a-f]+\(%rip\),%rax +# [0-9a-f]+ <.*>
|
|
+[a-f0-9]+: c3 ret *
|
|
#...
|
|
[0-9a-f]+ <call_func>:
|
|
+[a-f0-9]+: ff 25 ([0-9a-f]{2} ){4}[ ]+jmp \*0x[0-9a-f]+\(%rip\) +# [0-9a-f]+ <.*>
|
|
#pass
|