From owner-freebsd-current@freebsd.org Thu Jun 21 03:37:24 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 A5F8B10245FD; Thu, 21 Jun 2018 03:37:24 +0000 (UTC) (envelope-from arichardson.kde@gmail.com) Received: from mail-yw0-f179.google.com (mail-yw0-f179.google.com [209.85.161.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 460E584DAF; Thu, 21 Jun 2018 03:37:24 +0000 (UTC) (envelope-from arichardson.kde@gmail.com) Received: by mail-yw0-f179.google.com with SMTP id t198-v6so640571ywc.3; Wed, 20 Jun 2018 20:37:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4LUYW8vDYEdqRIQux+5ZhvpZPix7OEYYFWCORerQ+4I=; b=uJufNGZj7lnyWRvTFj80pr2N4K/Os30+8KdL67Skw/ZetBLVomwN1Y32ANVHtj5PS0 loJTX8oa2FCI4f8gKANxnEdLv5OEo5o7CSHmw9grXDBZ64x+SD5NRufYNL2O3iMavrj3 pJQlgtuPHWShEclFnWBMlEETD7VZmhfgdribDYTfYo1/HK6uSvPUvw6eZqld2lM4874Q 1m+d5ANG+eqN9waPhoo/Ev2KxmxmgNdE6Kf/JhTbc4/t6DxMWl6xrPsk+2ETYxRw4sYk o7txf9090kgWuPNTweeUToVJ/H5HIkO9aKoCUxgtxwG/8U7yJxsJkPquhHyO3gjEybF4 X2ng== X-Gm-Message-State: APt69E2cBI50HIUXtZDBmFX3KLlticJuY26p0B8h9QoyBTI71NK26tx9 jb8/TzUtGsJ/2zCp6Ly2YBVMpBLOlMrcyQ== X-Google-Smtp-Source: ADUXVKLFhNtO8zoxm+x5S3Jwimk88UDVF7nGYqXTlfnYnaZ6mBuE1IgOymn7enBjgvF30+Yv5GWC9Q== X-Received: by 2002:a81:6dc5:: with SMTP id i188-v6mr10890217ywc.385.1529530014025; Wed, 20 Jun 2018 14:26:54 -0700 (PDT) Received: from mail-yb0-f171.google.com (mail-yb0-f171.google.com. [209.85.213.171]) by smtp.gmail.com with ESMTPSA id f131-v6sm1220394ywh.18.2018.06.20.14.26.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Jun 2018 14:26:53 -0700 (PDT) Received: by mail-yb0-f171.google.com with SMTP id x6-v6so392051ybl.12; Wed, 20 Jun 2018 14:26:53 -0700 (PDT) X-Received: by 2002:a25:a443:: with SMTP id f61-v6mr11875773ybi.38.1529530013081; Wed, 20 Jun 2018 14:26:53 -0700 (PDT) MIME-Version: 1.0 References: <20180620155022.GA92001@spindle.one-eyed-alien.net> In-Reply-To: <20180620155022.GA92001@spindle.one-eyed-alien.net> From: Alexander Richardson Date: Wed, 20 Jun 2018 22:26:41 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Tool Chain Migration: objdump users, please test llvm-objdump To: Brooks Davis Cc: Ed Maste , FreeBSD Current , "freebsd-toolchain@FreeBSD.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 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: Thu, 21 Jun 2018 03:37:25 -0000 On Wed, 20 Jun 2018 at 16:50 Brooks Davis wrote: > 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. > > > > 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. > > > > 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). > > When I made the change to use llvm-objdump in CheriBSD I had to change the objdump flags from -xrsSd to -r -s -p -S -d -h -l -t. This is because llvm-objdump doesn't support the -x option and doesn't accept joined single-character options. I've been meaning to submit a patch upstream for -x but haven't got around to it yet. Otherwise the only noticeable change was that creating a full dump of any binary is MUCH faster. Alex