[lld] r262026 - Add comment on AMDGPU that the difference has no obvious reason.
Rui Ueyama via llvm-commits
llvm-commits at lists.llvm.org
Fri Feb 26 12:36:49 PST 2016
Right. All the stuff I saw in the AMDGPU support in the linker seems that
they are not stemmed from architecture-specific requirement but just to
deal with odd design choices of the file format which seems to have caused
by misunderstanding of the regular ELF spec. I don't think it's too late to
fix it -- I want to fix it.
On Fri, Feb 26, 2016 at 12:27 PM, Rafael Espíndola <
rafael.espindola at gmail.com> wrote:
> > We can probably model this within ELF by just putting each section
> inside a
> > PT_LOAD (or whatever getAmdgpuPhdr returns) with vaddr of 0.
> I am not sure we could call that an "address". The fundamental problem
> that needs to be solved is that there shouldn't be a special case for
> a program handling amd gpu or the XYZ cpu. It has to be possible to
> just read PT_LOAD and mmap them as usual.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-commits