[lld] r257023 - [ELF] Add AMDGPU support

Rui Ueyama via llvm-commits llvm-commits at lists.llvm.org
Tue Jan 19 14:31:22 PST 2016


On Tue, Jan 19, 2016 at 1:47 PM, Simon Atanasyan <simon at atanasyan.com>
wrote:

> On Wed, Jan 20, 2016 at 12:18 AM, Rafael EspĂ­ndola
> <llvm-commits at lists.llvm.org> wrote:
> > A thought that has been growing in my mind for some time: There has to
> > be a limit to how odd a system we support on trunk. If someone
> > proposes a backend that use PDP endian, 9 bit bytes and cray floats I
> > think we should just reject it.
> >
> > The main thing that started me thinking was MIPS, were there seems to
> > be an endless series of differences to compensate for some other
> > difference. IMHO it and LLVM would be better served by having by
> > having a clean V2 ABI on trunk and all of odd st_info, relocation
> > packing, hi/lo mapping in a vendor branch.
>
> I agree that MIPS is unusual architecture from the linker point of
> view. But other linkers like gold and mclinker have not too
> complicated design, fast and support MIPS together with other targets.
> I do not have ready solution for LLD but maybe ability to create
> target specific GOT sections, override iteration over relocations etc
> allow to isolate unusual MIPS code and does not pollute common code.
>
> Sure that does not mean that I like current MIPS ABI :)
>

I'm pretty sure that you don't necessarily like the current MIPS ABI. :) As
for me, I dislike part of the MIPS ABI which are different from the
mainstream ELF ABIs without any justifiable reason. The MIPS endian looks
really a baked in bug that happened to be in the early version of some Unix
for MIPS (I've never seen any mixed endian format in the wild except the
MIPS ELF.) It doesn't support .gnu.hash. It has odd HI/LO relocations, etc,
etc.

We indeed want to support the current MIPS ABI since that's after all the
current ABI, and I really appreciate your effort. However, beside that, I
think there should be some effort going on to update the ABI to resolve the
issues.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20160119/a695c273/attachment.html>


More information about the llvm-commits mailing list