Date: Thu, 21 Jun 2018 09:54:43 -0400 From: Ed Maste <emaste@freebsd.org> To: Alexander Richardson <arichardson@freebsd.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: <CAPyFy2BkgTviwZden4%2B9xRdaTu8Gp45QTtgkZND%2BxCtTQ0UTiA@mail.gmail.com> In-Reply-To: <CAPyFy2BpjYdLVx74aE=49dyOdWyS_GVymCch894XGjUC5Waw_w@mail.gmail.com> References: <CAPyFy2BYOhNFkNGGMSKgpN%2BxV=FvrLtSHc0DH3WQjQe2a9beeg@mail.gmail.com> <20180620155022.GA92001@spindle.one-eyed-alien.net> <CA%2BZ_v8rzL83Okabw--Az55wHnTVw=RanWH0yHoVNrqtfMpTJGg@mail.gmail.com> <CAPyFy2BpjYdLVx74aE=49dyOdWyS_GVymCch894XGjUC5Waw_w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 June 2018 at 09:09, Ed Maste <emaste@freebsd.org> wrote: > > We'll also need a man page. I took a quick look at this, and in doing so found that the output from "llvm-objdump --help" appears to be missing a large number of single-letter options, so one more thing to sort out. As it happens there are LLVM bugs open for a number of the llvm-objdump issues (even including some I submitted but forgot about): https://bugs.llvm.org/buglist.cgi?component=llvm-objdump&list_id=140941&product=tools&query_format=advanced&resolution=---
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2BkgTviwZden4%2B9xRdaTu8Gp45QTtgkZND%2BxCtTQ0UTiA>