--symbolize-operands When disassembling, symbolize a branch target operand to print a label instead of a real address.
Details
- Reviewers
jhenderson shchenz qiucf jsji MaskRay - Group Reviewers
Restricted Project - Commits
- rGb66328701a52: [PowerPC][llvm-objdump] enable --symbolize-operands for PowerPC ELF/XCOFF.
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/test/tools/llvm-objdump/ELF/PowerPC/elf-disassemble-symbolize-operands.yaml | ||
---|---|---|
7 | Add -NEXT: | |
43 | obj2yaml created test file has many redundant things which are noise, e.g. eh_frame, .note.GNU-stack, STT_FILE. They can all be deleted. How about using assembly with llvm-mc -filetype=obj? The main thing to test is the code sequence which is opaque as the yaml test (Content). An assembly test is easier to update. | |
llvm/tools/llvm-objdump/llvm-objdump.cpp | ||
981 | You can order PowerPC before X86 for an alphabetical order. |
llvm/test/tools/llvm-objdump/ELF/PowerPC/elf-disassemble-symbolize-operands.yaml | ||
---|---|---|
1 | Don't prefix test names with elf- if they're in an ELF subdirectory. | |
llvm/test/tools/llvm-objdump/XCOFF/disassemble-symbolize-operands.yaml | ||
17–18 | Similar comment to MaskRay's above - the input probably wants to just be IR or assembly. |
lld/test/ELF/ppc64-toc-call-to-pcrel.s | ||
---|---|---|
32–33 | The change is not so straightforward to me. Could we use <callee>:, <caller>:, <__toc_save_callee>: as the check label content? So it would not be confused with the new added branch target like <__toc_save_callee>. | |
llvm/test/tools/llvm-objdump/ELF/PowerPC/disassemble-symbolize-operands.ll | ||
1 ↗ | (On Diff #392618) | Can we add a case with internal/external function calls? |
3 ↗ | (On Diff #392618) | And maybe another case for CTR loop too?(for bdnz) |
llvm/test/tools/llvm-objdump/XCOFF/disassemble-symbolize-operands.ll | ||
2 ↗ | (On Diff #392618) | Can we show the leading-addr? As it can show whether the label matches the addr or not. |
- Address comments.
- Skip recording branches for function calls in collectLocalBranchTargets();
My comments have been addressed. Looks good, but leaving approval to someone who actually knows about the disassembly.
llvm/test/tools/llvm-objdump/ELF/PowerPC/disassemble-symbolize-operands.ll | ||
---|---|---|
29 ↗ | (On Diff #394497) | we can add an internal attribute for the internal function to make sure it is internally called in the function foo. For now, it is not internally called. I saw two external calls there. Linux system objdump can dump the internal function call as: 78: 89 ff ff 4b bl 0 <internal> So it's better llvm-objdump can also dump the internal function call like this. |
llvm/tools/llvm-objdump/llvm-objdump.cpp | ||
1002 | s/PowerPc/PowerPC/g | |
1004 | Can this logic be added in PPCMCInstrAnalysis? So we don't need the target check here. |
Address comments.
llvm/tools/llvm-objdump/llvm-objdump.cpp | ||
---|---|---|
1004 | I think we should return true for such cases in evaluateBranch(), because they are indeed branch operands, and their targets should be printed just like the behavior of system objdump when no --symbolize-operands is requires. 88: bl 0x88 <foo+0x48> 8c: nop |
LGTM. Thanks for adding this support.
One minor comment: need to update the doc for PowerPC for --symbolize-operands option in llvm-objdump.rst.
Better to wait for some days before committing.
llvm/test/tools/llvm-objdump/XCOFF/disassemble-symbolize-operands.ll | ||
---|---|---|
6 ↗ | (On Diff #395061) | This seems not right, expect .internal here. I guess it should be a legacy issue. Should be ok to do this in another patch. |
llvm/test/tools/llvm-objdump/XCOFF/disassemble-symbolize-operands.ll | ||
---|---|---|
6 ↗ | (On Diff #395061) | I will leave a TODO for this. |
The change is not so straightforward to me.
Could we use <callee>:, <caller>:, <__toc_save_callee>: as the check label content? So it would not be confused with the new added branch target like <__toc_save_callee>.