Date: Wed, 20 Jun 2018 19:31:21 -0400 From: Ed Maste <emaste@freebsd.org> To: Shawn Webb <shawn.webb@hardenedbsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, "freebsd-toolchain@FreeBSD.org" <freebsd-toolchain@freebsd.org> Subject: Re: Tool Chain Migration: objdump users, please test llvm-objdump Message-ID: <CAPyFy2BaPe7_Cq_3A0PsL4TK_oJGv7rFProQzE6VCU48i8Xjjw@mail.gmail.com> In-Reply-To: <20180620222527.vkd5fm3ksd5j6yux@mutt-hbsd> References: <CAPyFy2BYOhNFkNGGMSKgpN%2BxV=FvrLtSHc0DH3WQjQe2a9beeg@mail.gmail.com> <20180620222527.vkd5fm3ksd5j6yux@mutt-hbsd>
next in thread | previous in thread | raw e-mail | index | archive | help
On 20 June 2018 at 18:25, Shawn Webb <shawn.webb@hardenedbsd.org> wrote: > > Would you like me to quantify the compilation breakages due to the > full llvm toolchain switch? If so, I can do that after July 12th. Thanks Shawn, right now I'm interested specifically in llvm-objdump, with the goal of sorting it out in advance of FreeBSD 12. I think it's a worthwhile endeavour to quantify the breakage from using all of the LLVM tools though, and if you're able to triage the issues and submit LLVM, FreeBSD, or upstream port issues as appropriate that would be much appreciated. (It's just not yet on the critical path for me.)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2BaPe7_Cq_3A0PsL4TK_oJGv7rFProQzE6VCU48i8Xjjw>