This test case captures the current state of support for printing branch targets.
In most test/tools/, the prevailing continuation-line format is to place | at the line end.
# RUN: llvm-mc -filetype=obj -triple riscv32 -mattr=+c %s | # RUN: llvm-objdump -d -M no-aliases --no-show-raw-insn - |
The address formatting is checked by other tests so this test doesn't need to check it.
By removing addresses, when the number of instruction changes, the update (ongoing maintenance) will touch fewer lines.
For similar reasons, remove leading addresses.
I have a slight preference that instructions are indented by two: to be clearer that they belong to the function (nearest label).
60: c.nop should probably keep its address to be clear that its a jump target.
Thank for such a rapid review @MaskRay! I've left a couple of queries in response, but otherwise I'll refresh the test case once I've had feedback on other patches in the series (to minimise repeated rebase effort).
The reasoning behind --match-full-lines was that it will catch changes to printing of branch targets (as in D116678), ensuring the test case is updated.
Do you still feel it's worth doing, when taking into account the changes to this test in D116678?