From owner-svn-doc-head@freebsd.org Sun Jul 2 18:58:47 2017 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77FD1DAB31A; Sun, 2 Jul 2017 18:58:47 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2DDDF736B9; Sun, 2 Jul 2017 18:58:47 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id v62IwkpL051974; Sun, 2 Jul 2017 18:58:46 GMT (envelope-from bjk@FreeBSD.org) Received: (from bjk@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id v62Iwk20051973; Sun, 2 Jul 2017 18:58:46 GMT (envelope-from bjk@FreeBSD.org) Message-Id: <201707021858.v62Iwk20051973@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bjk set sender to bjk@FreeBSD.org using -f From: Benjamin Kaduk Date: Sun, 2 Jul 2017 18:58:46 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r50432 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head X-SVN-Commit-Author: bjk X-SVN-Commit-Paths: head/en_US.ISO8859-1/htdocs/news/status X-SVN-Commit-Revision: 50432 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2017 18:58:47 -0000 Author: bjk Date: Sun Jul 2 18:58:46 2017 New Revision: 50432 URL: https://svnweb.freebsd.org/changeset/doc/50432 Log: Add 2017Q2 LLD entry from emaste Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2017-04-2017-06.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2017-04-2017-06.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2017-04-2017-06.xml Sun Jul 2 18:25:17 2017 (r50431) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2017-04-2017-06.xml Sun Jul 2 18:58:46 2017 (r50432) @@ -363,4 +363,76 @@ The &os; Foundation + + + Using LLVM's LLD Linker as &os;'s System Linker + + + + + Rafael + Espíndola + + rafael.espindola@gmail.com + + + + + Ed + Maste + + emaste@FreeBSD.org + + + + + &os; lld Wiki Page + &os;/LLD Tracking PR (LLVM Bugzilla) + Exp-Run Request Using lld as /usr/bin/ld + + + +

LLD is the linker in the LLVM family of projects. It is a + high-performance linker that supports the ELF, COFF and + Mach-O object formats. It is broadly compatible with the + common linkers used for each file format. For ELF this is + the GNU Binary File Descriptor (BFD) ld and GNU + gold. However, LLD's authors are not constrained + by strict compatibility where it would hamper performance or + desired functionality.

+ +

LLD is now used as the default system linker for + &os;/arm64 and can link a working kernel, modules, and + userland for &os;/amd64. LLD can also link a working + kernel and modules (but not userland) for &os;/arm and + &os;/i386.

+ +

Work is ongoing to address ports that do not build with LLD + as the system linker (either by fixing the port, or + configuring the port to be linked by GNU ld).

+ +

For &os; 12.0 we expect to use LLD as the system linker for + the same set of architectures that use Clang by default: + 32- and 64-bit arm and x86.

+ + + The &os; Foundation + + + Fix libtool to detect LLD and pass the same + command line arguments as for GNU ld and + gold. + + Investigate remaining amd64 and arm64 port + build failures. + + Investigate and improve LLD on i386 and arm, before + the creation of the stable/12 branch. + + Investigate and improve LLD on all other + architectures. + + Extensive testing. + +