From owner-freebsd-current@freebsd.org Wed Jun 20 15:50:31 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63001102067A; Wed, 20 Jun 2018 15:50:31 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0879380D0C; Wed, 20 Jun 2018 15:50:30 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id B6A4E5A9F12; Wed, 20 Jun 2018 15:50:22 +0000 (UTC) Date: Wed, 20 Jun 2018 15:50:22 +0000 From: Brooks Davis To: Ed Maste Cc: FreeBSD Current , "freebsd-toolchain@FreeBSD.org" Subject: Re: Tool Chain Migration: objdump users, please test llvm-objdump Message-ID: <20180620155022.GA92001@spindle.one-eyed-alien.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7JfCtLOvnd9MIVvH" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2018 15:50:31 -0000 --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--