binutils-gdb/ld/testsuite/ld-x86-64/pr26018.d

#as: --64
#ld: -shared -Bsymbolic-functions -melf_x86_64
#objdump: -dw

.*: +file format .*


Disassembly of section .text:

[0-9a-f]+ <_start>:
 +[a-f0-9]+:	e8 00 00 00 00       	call   [0-9a-f]+ <foo>

[0-9a-f]+ <foo>:
 +[a-f0-9]+:	c3                   	ret *
#pass
ld: Add -Bsymbolic-functions tests PR ld/26018 * testsuite/ld-i386/i386.exp: Add a -Bsymbolic-functions test. * testsuite/ld-x86-64/x86-64.exp: Likewise. * testsuite/ld-i386/pr26018.d: New file. * testsuite/ld-x86-64/pr26018.d: Likewise. * testsuite/ld-x86-64/pr26018.s: Likewise. 2020-05-24 11:49:16 +08:00			`#as: --64`
			`#ld: -shared -Bsymbolic-functions -melf_x86_64`
			`#objdump: -dw`

			`.: +file format .`


			`Disassembly of section .text:`

			`[0-9a-f]+ <_start>:`
x86: avoid attaching suffixes to unambiguous insns "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. 2020-07-15 14:53:55 +08:00			`+[a-f0-9]+: e8 00 00 00 00 call [0-9a-f]+ <foo>`
ld: Add -Bsymbolic-functions tests PR ld/26018 * testsuite/ld-i386/i386.exp: Add a -Bsymbolic-functions test. * testsuite/ld-x86-64/x86-64.exp: Likewise. * testsuite/ld-i386/pr26018.d: New file. * testsuite/ld-x86-64/pr26018.d: Likewise. * testsuite/ld-x86-64/pr26018.s: Likewise. 2020-05-24 11:49:16 +08:00
			`[0-9a-f]+ <foo>:`
x86: avoid attaching suffixes to unambiguous insns "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. 2020-07-15 14:53:55 +08:00			`+[a-f0-9]+: c3 ret *`
ld: Add -Bsymbolic-functions tests PR ld/26018 * testsuite/ld-i386/i386.exp: Add a -Bsymbolic-functions test. * testsuite/ld-x86-64/x86-64.exp: Likewise. * testsuite/ld-i386/pr26018.d: New file. * testsuite/ld-x86-64/pr26018.d: Likewise. * testsuite/ld-x86-64/pr26018.s: Likewise. 2020-05-24 11:49:16 +08:00			`#pass`