Date: Tue, 24 Jul 2012 12:48:27 +0100 From: David Chisnall <theraven@FreeBSD.org> To: Erik Cederstrand <erik@cederstrand.dk> Cc: freebsd-toolchain@FreeBSD.org, Dimitry Andric <dim@FreeBSD.org> Subject: Re: MCLinker and llvm-config Message-ID: <282B3A4F-4196-4506-ABC0-E8DB9B991649@FreeBSD.org> In-Reply-To: <C6BBA96D-CDB4-41E0-8399-8C3293AA4EB1@cederstrand.dk> References: <88204636-7665-4B06-B781-174C24A384FE@cederstrand.dk> <500E6798.9040104@FreeBSD.org> <C6BBA96D-CDB4-41E0-8399-8C3293AA4EB1@cederstrand.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24 Jul 2012, at 10:39, Erik Cederstrand wrote: > Btw, do you guys have any plans for a GNU ld replacement? Progress on = the more "official" lld (http://lld.llvm.org/) seems slow, and MCLinker = more promising. Hence my feeble attempts :-) Most of the progress in lld is not in lld itself, but in the underlying = frameworks. The tool is expected to be a fairly thin wrapper. The = Object code in the main llvm repository is where the real work happens. MCLinker is likely a dead end. It was intended as a quick-and-dirty = hack to get a working linker for a small subset of the problem, with no = thought as to how to solve the general case. David=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?282B3A4F-4196-4506-ABC0-E8DB9B991649>