Date: Mon, 06 Aug 2012 14:44:27 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: Erik Cederstrand <erik@cederstrand.dk> Cc: freebsd-toolchain@freebsd.org, David Chisnall <theraven@theravensnest.org> Subject: Re: BSD archive file formats Message-ID: <501FBC2B.70906@FreeBSD.org> In-Reply-To: <C13E182F-56E1-43B9-9B9D-620238E6BA40@cederstrand.dk> References: <CANWS6nfWO8WvVXeRVB=YrFhhc-GT1Yo%2Bxx38OcitpN-Puhuw=A@mail.gmail.com> <C65466F5-5D93-4EDF-92B8-A1207FC34B72@theravensnest.org> <CANWS6neR0s%2BDteqRDkHX6Rb0dej%2Bi9TEDpmHAV53XzZ%2BD8141w@mail.gmail.com> <9F286684-EA0B-4F6F-8C1F-0036DF9A0C53@bsdimp.com> <C13E182F-56E1-43B9-9B9D-620238E6BA40@cederstrand.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2012-08-06 14:16, Erik Cederstrand wrote: ... > To do that, it would be helpful if our LLVM is updated to something later than r160433, since our version in CURRENT needs patching for MCLinker to work. I've asked dim@, but no reply yet. As far I know, we try to follow official LLVM releases in CURRENT. In that case, I guess LLVM 3.2 will happen around December 2012. I'm working on importing a new clang snapshot (from trunk, so version 3.2), on request from Brooks and others. It's going to take a little while, though. This is not because it is tricky to import it into the tree as-is, but because this new version triggers a whole bunch of new warnings, that I have to verify the fixes for with several people. :) Fur -current, I see no big trouble with using a snapshot, as long as it is reasonably stable. That is, it must be able to build itself flawlessly, survive all of llvm and clang's own regression tests, and obviously, build world, kernel and a reasonable set of ports. That said, I do remember you asked me to import a specific changelist from upstream to make MCLinker build. I will do so tonight, probably.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?501FBC2B.70906>