Custom Query (27 matches)
Results (4 - 6 of 27)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#29 | wontfix | Replace AmdKernelArg by AmdKernelArgInput | matszpk | matszpk |
Description |
Make AmdKernelArg? more descriptive (with all fields) by replacing it by AmdKernelArgInput? (from AmdBinGen?). |
|||
#28 | fixed | Add relocations support to GalliumCompute binary format (scratch buffer handling) | matszpk | matszpk |
Description |
Add relocations support to Gallium binary format (for support scratch buffer):
|
|||
#27 | invalid | Invalid binaries when assembling from source using .kernel .config versus .metadata | matszpk | NDBob95 |
Description |
Not sure if this is a known issue or if I am missing something in the documentation. I have been experimenting with your assembler/disassembler for a project I'm working on and I'm having trouble utilizing LDS from my custom code. Here is what I am seeing: 1) I take a saved binary of my original OpenCL code which works and disassemble using "clrxdisasm --all". 2) I rebuild the binary from source as-is using "clrxasm --64 --gpuType Ellesmere" using the raw disassembler output (with binary kernel metadata and setup) and it runs fine. 3) I take the same binary and disassemble with text config using "clrxdisasm --config --all". 4) I rebuild the binary from the text config source and it does not appear to be able to access LDS --- Operations not involving LDS are returning correct answers, the CodeXL Profiler shows LDS instructions being executed, but there is no data returned by any of the LDS path operations. 5) I disassemble the second binary using "clrxdisasm --all" to compare --- the two are identical except for the .kernel section, where the ".config" based binary appears to be missing a substantial amount of configuration metadata. Both binaries disassemble to the same text based config output:
|