Date: Wed, 20 Jun 2018 15:50:22 +0000 From: Brooks Davis <brooks@freebsd.org> To: Ed Maste <emaste@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: <20180620155022.GA92001@spindle.one-eyed-alien.net> In-Reply-To: <CAPyFy2BYOhNFkNGGMSKgpN%2BxV=FvrLtSHc0DH3WQjQe2a9beeg@mail.gmail.com> References: <CAPyFy2BYOhNFkNGGMSKgpN%2BxV=FvrLtSHc0DH3WQjQe2a9beeg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--7JfCtLOvnd9MIVvH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 20, 2018 at 10:46:46AM -0400, Ed Maste wrote: > Work is in progress to migrate fully to modern and permissively > licensed components for the tool chain. This includes moving away from > the three obsolete binutils components that are still in the base > system (as, ld, objdump). objdump is a tool to report information > about binary objects (such as headers, symbols, etc.), is not required > as a build tool, and in any case many uses of objdump are better > served by readelf. >=20 > For FreeBSD 12 I intend to remove GNU objdump 2.17.50. PR 229046[1] is > open to track tasks related to its removal, and users who need GNU > objdump can install an up-to-date version from the ports tree or the > binutils package. >=20 > That said, llvm includes a somewhat equivalent llvm-objdump, and it is > built by default in FreeBSD now. If llvm-objdump's command line option > support and output format is "close enough" to GNU objdump for most > users we may decide to install it as /usr/bin/objdump. Therefore, I > would like to ask users of GNU objdump in FreeBSD to give llvm-objdump > a try. Please let me know if it works for your uses, or describe > deficiencies that you found. I think we've changed our flag us in CheriBSD to accommodate llvm-objdump so at least a few months ago flag compatibility was poor. The output is different, but fine for my uses (producing human readable assembly output). -- Brooks --7JfCtLOvnd9MIVvH Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJbKne9AAoJEKzQXbSebgfA7uAH/2xPXhLzGp20uqe/KwYrdjm5 zeol32twuy23tuwUsxS/cqFK0uR7ZafA3pC4aOLKWa72EbOnKE5IqCqn729yn59+ yb/leR0KOZ3IVbAGinM/yyQEYhQSkHCJYwA+zyTY8oIP1PmRBy0eVNAaMwIYk4eq b+5W/KgrdJkK4N2Z6le2I6gd1skAr4fZ/gbZUxPH/IyEfykNgu0aJa546WAxm38u 0RgNOv47X7Ln3nqGJMlbOP/ji4VzaCQZcfuyNJKh5nh1sc7+++3k6UWZCOoXyh/Y LZuy5mkQbSrB/uMmoKlyy2H4jiGGIr6yUTWlZCA+nkEnv2zb4y29XZ3nwzYTmAQ= =y0r2 -----END PGP SIGNATURE----- --7JfCtLOvnd9MIVvH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180620155022.GA92001>