diff options
author | Andrew Burgess <aburgess@redhat.com> | 2022-09-02 18:15:30 +0100 |
---|---|---|
committer | Andrew Burgess <aburgess@redhat.com> | 2022-11-01 09:32:13 +0000 |
commit | 8cb6e17571f3fb66ccd4fa19f881602542cd06fc (patch) | |
tree | e55c7d09de4ee64ed49f0c9b8b345b2f666ce0de /ld/testsuite/ld-arm/farcall-mixed-lib.d | |
parent | 1751ca43fdae8d19e13ae55430700a60eb0f30d3 (diff) | |
download | fsf-binutils-gdb-8cb6e17571f3fb66ccd4fa19f881602542cd06fc.zip fsf-binutils-gdb-8cb6e17571f3fb66ccd4fa19f881602542cd06fc.tar.gz fsf-binutils-gdb-8cb6e17571f3fb66ccd4fa19f881602542cd06fc.tar.bz2 |
opcodes/arm: use '@' consistently for the comment character
Looking at the ARM disassembler output, every comment seems to start
with a ';' character, so I assumed this was the correct character to
start an assembler comment.
I then spotted a couple of places where there was no ';', but instead,
just a '@' character. I thought that this was a case of a missing
';', and proposed a patch to add the missing ';' characters.
Turns out I was wrong, '@' is actually the ARM assembler comment
character, while ';' is the statement separator. Thus this:
nop ;@ comment
is two statements, the first is the 'nop' instruction, while the
second contains no instructions, just the '@ comment' comment text.
This:
nop @ comment
is a single 'nop' instruction followed by a comment. And finally,
this:
nop ; comment
is two statements, the first contains the 'nop' instruction, while the
second contains the instruction 'comment', which obviously isn't
actually an instruction at all.
Why this matters is that, in the next commit, I would like to add
libopcodes syntax styling support for ARM.
The question then is how should the disassembler style the three cases
above?
As '@' is the actual comment start character then clearly the '@' and
anything after it can be styled as a comment. But what about ';' in
the second example? Style as text? Style as a comment?
And the third example is even harder, what about the 'comment' text?
Style as an instruction mnemonic? Style as text? Style as a comment?
I think the only sensible answer is to move the disassembler to use
'@' consistently as its comment character, and remove all the uses of
';'.
Then, in the next commit, it's obvious what to do.
There's obviously a *lot* of tests that get updated by this commit,
the only actual code changes are in opcodes/arm-dis.c.
Diffstat (limited to 'ld/testsuite/ld-arm/farcall-mixed-lib.d')
-rw-r--r-- | ld/testsuite/ld-arm/farcall-mixed-lib.d | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/ld/testsuite/ld-arm/farcall-mixed-lib.d b/ld/testsuite/ld-arm/farcall-mixed-lib.d index ef21428..3925e7d 100644 --- a/ld/testsuite/ld-arm/farcall-mixed-lib.d +++ b/ld/testsuite/ld-arm/farcall-mixed-lib.d @@ -6,26 +6,26 @@ start address 0x.* Disassembly of section .plt: .* <.plt>: - .*: e52de004 push {lr} ; \(str lr, \[sp, #-4\]!\) - .*: e59fe004 ldr lr, \[pc, #4\] ; .* <.*> + .*: e52de004 push {lr} @ \(str lr, \[sp, #-4\]!\) + .*: e59fe004 ldr lr, \[pc, #4\] @ .* <.*> .*: e08fe00e add lr, pc, lr .*: e5bef008 ldr pc, \[lr, #8\]! .*: .* .* <app_func@plt>: .*: e28fc6.* add ip, pc, #.* - .*: e28cca.* add ip, ip, #.* ; 0x.* + .*: e28cca.* add ip, ip, #.* @ 0x.* .*: e5bcf.* ldr pc, \[ip, #.*\]!.* .* <app_func_weak@plt>: .*: e28fc6.* add ip, pc, #.* - .*: e28cca.* add ip, ip, #.* ; 0x.* + .*: e28cca.* add ip, ip, #.* @ 0x.* .*: e5bcf.* ldr pc, \[ip, #.*\]!.* .* <lib_func3@plt>: .*: e28fc6.* add ip, pc, #.* - .*: e28cca.* add ip, ip, #.* ; 0x.* + .*: e28cca.* add ip, ip, #.* @ 0x.* .*: e5bcf.* ldr pc, \[ip, #.*\]!.* .* <lib_func4@plt>: .*: e28fc6.* add ip, pc, #.* - .*: e28cca.* add ip, ip, #.* ; 0x.* + .*: e28cca.* add ip, ip, #.* @ 0x.* .*: e5bcf.* ldr pc, \[ip, #.*\]!.* Disassembly of section .text: @@ -51,22 +51,22 @@ Disassembly of section .text: #... .* <__lib_func3_from_thumb>: - .*: e59fc000 ldr ip, \[pc\] ; .* <__lib_func3_from_thumb\+0x8> + .*: e59fc000 ldr ip, \[pc\] @ .* <__lib_func3_from_thumb\+0x8> .*: e08ff00c add pc, pc, ip .*: feffff.. .word 0xfeffff.. .* <__app_func_weak_from_thumb>: - .*: e59fc000 ldr ip, \[pc\] ; .* <__app_func_weak_from_thumb\+0x8> + .*: e59fc000 ldr ip, \[pc\] @ .* <__app_func_weak_from_thumb\+0x8> .*: e08ff00c add pc, pc, ip .*: feffff.. .word 0xfeffff.. .* <__lib_func4_from_thumb>: - .*: e59fc000 ldr ip, \[pc\] ; .* <__lib_func4_from_thumb\+0x8> + .*: e59fc000 ldr ip, \[pc\] @ .* <__lib_func4_from_thumb\+0x8> .*: e08ff00c add pc, pc, ip .*: feffff.. .word 0xfeffff.. .* <__app_func_from_thumb>: - .*: e59fc000 ldr ip, \[pc\] ; .* <__app_func_from_thumb\+0x8> + .*: e59fc000 ldr ip, \[pc\] @ .* <__app_func_from_thumb\+0x8> .*: e08ff00c add pc, pc, ip .*: feffff.. .word 0xfeffff.. ... @@ -78,12 +78,12 @@ Disassembly of section .text: #... .* <__app_func_weak_from_thumb>: - .*: e59fc000 ldr ip, \[pc\] ; .* <__app_func_weak_from_thumb\+0x8> + .*: e59fc000 ldr ip, \[pc\] @ .* <__app_func_weak_from_thumb\+0x8> .*: e08ff00c add pc, pc, ip .*: fdffff40 .word 0xfdffff40 .* <__app_func_from_thumb>: - .*: e59fc000 ldr ip, \[pc\] ; .* <__app_func_from_thumb\+0x8> + .*: e59fc000 ldr ip, \[pc\] @ .* <__app_func_from_thumb\+0x8> .*: e08ff00c add pc, pc, ip .*: fdffff28 .word 0xfdffff28 ... |