Details
Diff Detail
Event Timeline
include/llvm/Object/RelocVisitor.h | ||
---|---|---|
144–146 ↗ | (On Diff #60885) | This processes HI relocations as LO. Should not LO and HI be processed differently, or am I missing something? |
include/llvm/Object/RelocVisitor.h | ||
---|---|---|
144–146 ↗ | (On Diff #60885) | The RelocVisitor seems to only be used in DwarfContext.cpp. It's not clear me what it's even supposed to do with absolute relocations. Is this code even necessary? |
include/llvm/Object/RelocVisitor.h | ||
---|---|---|
144–146 ↗ | (On Diff #60885) | I think at this point we will only need to handle R_AMDGPU_ABS32 in RelocVisitor, since we are going to use it for dwarf relocs |
Split changes outside of lib/Target/AMDGPU into a new patch: http://reviews.llvm.org/D21443
test/CodeGen/AMDGPU/large-alloca-compute.ll | ||
---|---|---|
5 | Why do you need to use "llc -filetype=obj"? Please split this into tow tests. One prints assembly and checks it. |
Lgtm, but I have a question:
Will SCRATCH_RSRC_DWORD also need special treatment in the linker? If so
we should have special relocations for it to avoid using names in the
linker. This is similar to how the got position is accessed: magical name
for the assembler, different relocation for the linker.
Cheers,
Rafael
This won't need any special handling in the linker. This is only used by our legacy path which does not use lld at all.
Why do you need to use "llc -filetype=obj"?
Please split this into tow tests. One prints assembly and checks it.
Another parses assembly and checks the relocations.