Instruction offset

[adam-yang]

Hi,
I'm trying to construct the control flow graph from asm using the IsaDecoder. The branch instructions give the branch offset, but there's no information about instruction's offsets. Is there a way to achieve what I'm trying to do?

Thanks.

[AmitBM]

Hi @adam-yang,

Did you use DecodeShaderDisassemblyText() / DecodeShaderDisassemblyFile() with resolve_direct_branch_targets set to true? You will need to decode the whole shader in order to enable branch resolution.

[adam-yang]

Here's all the input I've tried (all except the binary file attached):

1. Dissassembly (attached)
2. Content from .text section from the binary ELF

For both was able to see inst.instruction_semantic_info.branch_info.branch_offset, but no branch target information was available. It looks like the disassembly was not being used at all, and IsaDecoder was using the information in the comments? Is this the intended final behaviour?

Would it be feasible for IsaDecoder to give the offset for each instruction, this way I can use branch_info.branch_offset to figure out the control flow, as well as use the offset to find source mapping from debug info?

This assembly is from RDNA 3.5.
s_code_end was also being shown as a branch.

simple.asm.txt
simple_from_elf.asm.txt

[AmitBM]

Hi @adam-yang,

Are you getting BranchInfo::branch_target_index populated? That field should give you the index of the target instruction within the Decode* function's output vector (std::vector<InstructionInfoBundle>).

-=-=-=-

Regardless -
How did you generate the disassembly? It is "non-standard" (compared with the shader disassembly format that AMD tools normally produce):

1. simple_asm.txt does not contain any labels (for branch targets).
2. simple_from_elf.asm.txt does not contain the standard comment (// <offset>: <binary representation>).

Also please note that the label name format is unusual as well (".L*") - this may cause issues with some other AMD tools but shouldn't impact IsaDecoder.

The IsaDecoder API currently relies on the disassembly format being "standard". That is why you did not get all branch metadata fields populated. Item '1' above can be addressed (the presence of labels should not impact branch resolution) - that should be fixed. Item '2' above is required by the IsaDecoder API in its current implementation. It would be good if you could work with the "standard" AMD disassembly format if you are planning to leverage the isa_spec_manager toolset.