-
Notifications
You must be signed in to change notification settings - Fork 546
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
i#6662 public traces, part 3: regdeps disasm #6799
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
regdeps instructions.
Spacing is important there, cannot be changed.
stay within 90 chars lines.
modifying it for all arches.
edeiana
commented
May 8, 2024
edeiana
commented
May 8, 2024
There are 2 tests consistently failing in ci-x86 / x86-64: EDIT: this has been fixed. |
encodings have at least a 4 byte header and are 4 byte aligned, so let's take advantage of that.
Does this test run in arm and riscv?
edeiana
changed the title
i#6662 public traces, part 3: view tool
i#6662 public traces, part 3: regdeps disasm
May 16, 2024
edeiana
commented
May 16, 2024
derekbruening
approved these changes
May 16, 2024
For ARM this test fails because of "/lib/ld-linux-armhf.so.3: No such file or directory". Added FIXME comment about it.
edeiana
added a commit
that referenced
this pull request
May 17, 2024
Modifies the view tool to handle OFFLINE_FILE_TYPE_ARCH_REGDEPS traces, leveraging the disassembly of DR_ISA_REGDEPS instructions. When visualizing DR_ISA_REGDEPS instructions, the view tool still prints the instruction length and PC, which for OFFLINE_FILE_TYPE_ARCH_REGDEPS traces are the same as those in the original trace. Then, after the PC, the instruction encoding, categories, operation size, and registers are printed following the disassembly format of DR_ISA_REGDEPS instructions (xref: #6799). DR_ISA_REGDEPS instructions printed by the view tool look as follows: ``` [...] ifetch 10 byte(s) @ 0x00007f86ef03d107 00001931 04020204 load store [4byte] %rv0 %rv2 %rv36 -> %rv0 [...] 00000026 ``` We also fix a formatting bug in DR_ISA_REGDEPS instruction disassembly, where we were missing a new line when the instruction encoding spills into a second line. Issue: #6662
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds disassembling for DR_ISA_REGDEPS instructions.
Specifically, when we disassemble DR_ISA_REGDEPS instructions, we print the
instruction encoding (divided in 4 byte words, can span one or two lines, similar to x86),
we substitute the opcode with categories, we print the operations size (e.g.,
[4byte]
),and then the source and destination virtual register names (e.g.,
%rv3
).Disassembled instructions look as follows:
00000812 06260606 load [8byte] %rv4 -> %rv4 %rv36
In general, they follow this pattern:
[encoding (in 4 byte words)] [categories] [operation_size] [src_regs -> dst_regs]
Issue: #6662