Open 1e-to opened 3 years ago
Also in the .asm file at /tmp/IntelIGC/pytho_xxxxxx/ there is nothing interesting about nested functions and debugging information, only the code
Also I checked the dbg file (type data), but there is nothing there either
hexdump -C xxxx.dbg > dump.txt
Output
@mingjie-intel the information in the ticket are useful if we want to go one level lower than SPIR-V and look at the IGC compiled binaries.
When set to “1”, IGC will write number of dumps into /tmp/IntelIGC.
To read the DWARF of a kernel, we first need a copy of the IGC generated kernel binary. To do that, run the Python script in a debugger, and set a breakpoint in the kernel:
Once the breakpoint hits, the kernel has been generated and offloaded. At that point, the IGFX driver (i.e. our debugger driver) has copied the kernel into a file, and saved it at /tmp. All files saved at /tmp/IntelIGC/pytho_xxxxxx/
Then, to read the DWARF in that kernel binary (elf), use tool llvm-dwarfdump. The app outputs the contents of the DWARF. So for example, to create a text file DWARF.dump with the contents of the DWARF data:
!Nested function information is missing here!