From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 9 15:36:23 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5D965952 for ; Mon, 9 Mar 2015 15:36:23 +0000 (UTC) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) by mx1.freebsd.org (Postfix) with ESMTP id 37FC3A16 for ; Mon, 9 Mar 2015 15:36:23 +0000 (UTC) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id D9B7B5A9F27; Mon, 9 Mar 2015 15:36:22 +0000 (UTC) Date: Mon, 9 Mar 2015 15:36:22 +0000 From: Brooks Davis To: Jonathon McDaniels Subject: Re: GSoC idea - porting and patching of userland for lld, the LLVM linker Message-ID: <20150309153622.GB72806@spindle.one-eyed-alien.net> References: <54F9EFD7.7030803@mymail.vcu.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gatW/ieO32f1wygP" Content-Disposition: inline In-Reply-To: <54F9EFD7.7030803@mymail.vcu.edu> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2015 15:36:23 -0000 --gatW/ieO32f1wygP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 06, 2015 at 01:20:07PM -0500, Jonathon McDaniels wrote: > Hey guys, >=20 > After giving it some thought, I was thinking of porting ( as in, make it= =20 > a port of ) and patching the userland so a make buildworld can go=20 > through on x86/AMD64 on lld, the LLVM linker, and if time permits,=20 > patching the kernel to make use of it.. As the binutils included in base= =20 > is over 7 years old, and is unlikely to be updated due to the GPLv3, it= =20 > would make sense to assist with removing dependence of the FreeBSD=20 > platforms now using LLVM/Clang for compiling. >=20 > Before I go contact the mentors that would be within the scope of this=20 > project, I wanted to make sure of the following: >=20 > * That this would be a good use of GSoC > * That it is narrow enough in scope to be feasible, but broad enough > that it would prove a beneficial project. >=20 > Considering the environment we have now, I think it would allow me to=20 > further my knowledge of C beyond what I already know ( currently working= =20 > on learning about dynamic linking of libraries, and I already know about= =20 > data structures, stacks, pointers etc. and plan to be much farther along= =20 > by the time of the start of the project and deliverables. ). >=20 > And since lld is compatible with the BSD license terms, and is=20 > interoperable with LLVM, it seems a viable and good project to undertake. >=20 > Thoughts from you guys? Not to be too discouraging, I want lld in the base soon, but I'm not convinced there's a good GSoC project here. Creating a port of lld is probably a week's work even starting with no knowledge of the ports system. There may be some FreeBSD specific changes to lld required, but they should be small. Resolving compatibility issues with FreeBSD and ports might be a good project, but being able to work on that depends on the completion of linker script support. I think that's an unacceptably large external dependency for a GSoC project given that there's no public timeline for that work. -- Brooks --gatW/ieO32f1wygP Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlT9vfYACgkQXY6L6fI4GtRswwCcCauyHT7VOyE01OgB3RiAKuwt EqwAnRgf8zq8lpawSxB9qThJfc0EtzX7 =yuUm -----END PGP SIGNATURE----- --gatW/ieO32f1wygP--