llvm dev - Feb 2017 - Compatibility issue with go

I spent most of the day trying to figure out why go packages were
failing to build when lld was the system linker.

I finally got to what IMHO is an issue in go:
https://github.com/golang/go/issues/19018.

I will still give it a try tomorrow to see how hard it would be to work
around it in lld, but just wanted to share in case anyone else was
hitting the same problem.

Cheers,
Rafael

Does Go use the system linker? Go is written in Go, and I was thinking that
the Go toolchain includes everything from a compiler to a standard library
to a linker, and depends on very little on the host system.

On Thu, Feb 9, 2017 at 4:02 PM, Rafael Avila de Espindola <
rafael.espindola at gmail.com> wrote:
> I spent most of the day trying to figure out why go packages were
> failing to build when lld was the system linker.
>
> I finally got to what IMHO is an issue in go:
> https://github.com/golang/go/issues/19018.
>
> I will still give it a try tomorrow to see how hard it would be to work
> around it in lld, but just wanted to share in case anyone else was
> hitting the same problem.
>
> Cheers,
> Rafael
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170209/28c3fad8/attachment.html>

Rui Ueyama <ruiu at google.com> writes:
> Does Go use the system linker? Go is written in Go, and I was thinking that
> the Go toolchain includes everything from a compiler to a standard library
> to a linker, and depends on very little on the host system.
Looks like all that they are missing is "ld -r" :-(

Cheers,
Rafael