aboutsummaryrefslogtreecommitdiff
path: root/ld/testsuite/ld-arm/farcall-arm-arm.d
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2022-09-02 18:15:30 +0100
committerAndrew Burgess <aburgess@redhat.com>2022-11-01 09:32:13 +0000
commit8cb6e17571f3fb66ccd4fa19f881602542cd06fc (patch)
treee55c7d09de4ee64ed49f0c9b8b345b2f666ce0de /ld/testsuite/ld-arm/farcall-arm-arm.d
parent1751ca43fdae8d19e13ae55430700a60eb0f30d3 (diff)
downloadfsf-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-arm-arm.d')
-rw-r--r--ld/testsuite/ld-arm/farcall-arm-arm.d2
1 files changed, 1 insertions, 1 deletions
diff --git a/ld/testsuite/ld-arm/farcall-arm-arm.d b/ld/testsuite/ld-arm/farcall-arm-arm.d
index 7ee6d66..76a1335 100644
--- a/ld/testsuite/ld-arm/farcall-arm-arm.d
+++ b/ld/testsuite/ld-arm/farcall-arm-arm.d
@@ -7,7 +7,7 @@ Disassembly of section .text:
1004: 00000000 andeq r0, r0, r0
00001008 <__bar_veneer>:
- 1008: e51ff004 ldr pc, \[pc, #-4\] ; 100c <__bar_veneer\+0x4>
+ 1008: e51ff004 ldr pc, \[pc, #-4\] @ 100c <__bar_veneer\+0x4>
100c: 02001020 .word 0x02001020
Disassembly of section .foo: