From owner-freebsd-toolchain@FreeBSD.ORG Fri Sep 26 17:32:23 2014 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 08F9A3AD for ; Fri, 26 Sep 2014 17:32:23 +0000 (UTC) Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BE949B8A for ; Fri, 26 Sep 2014 17:32:22 +0000 (UTC) Received: by mail-qa0-f47.google.com with SMTP id i13so6044448qae.20 for ; Fri, 26 Sep 2014 10:32:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=GimN+mWLPjMIab/dm5Djl6A1+j3IBSL/OvWbEPUL8WE=; b=Ol+FgRrzYborf6rzQaLYMXPlFWdSfBDiB7ykYnv2Wf0fY76RJGyxb8GdGcYuWHxQDd g5QaEd+EKnlX5jEtSb6yxj3VBAlHdI45DU1g362u4GANerLKNRMd+XXRpalX0BAnmwXZ PGY4eiRB2W0HihJzFnvOn5CC2+0Si0sId3aBJoamr3Ywm6wPha556FpXwXtaWvBot0dS uo5vVS0Khn2aXjidaZ0ZAF6wCrAkMasqoGNzH3FqPqVvcL3S0qYIGKlW0XqLrQ6I2n6T gxU8CEQSInnZNzkk/Gd0yX6BBb3RQHot9InbPiOgXPduT8I9NBApWbkAwZNJhZ03HLWw joMw== X-Gm-Message-State: ALoCoQmnSPkY2pF3gJHUbF1A4m+a+EOx5FnHPGsYlDnr3clL0oj+iVqp7RsI89CmThGxmCfp65zA MIME-Version: 1.0 X-Received: by 10.224.32.138 with SMTP id c10mr18189167qad.1.1411752741041; Fri, 26 Sep 2014 10:32:21 -0700 (PDT) Received: by 10.140.16.183 with HTTP; Fri, 26 Sep 2014 10:32:20 -0700 (PDT) Date: Fri, 26 Sep 2014 11:32:20 -0600 Message-ID: Subject: Re: elftoolchain update? From: Will Andrews To: jkoshy@freebsd.org, kaiw@freebsd.org, freebsd-toolchain@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2014 17:32:23 -0000 Hi, I've created a git-svn clone of the current elftoolchain, and applied some fixes in a branch: https://github.com/wca/elftoolchain/tree/freebsd Any objections if I update the copy in head using this branch? I've heard nothing from either Kai or Joseph. I'm not done testing yet -- it looks like there are some more bugfixes needed to get ctfconvert to at least run against C++ object files without bailing. Just wanted to know if there are any specific concerns that people might have. A related review involves an update for the ELF headers: https://reviews.freebsd.org/D844 I haven't finished testing this either (need to do an universe build to check for conflicts), but my goal here is to achieve header parity with from elftoolchain, which is largely duplicate. The elftoolchain header exports many more symbols that are used by its userland programs. This would include arch-specific interpretations of some ELF structures. I believe it's appropriate to export these on a global basis, given that userland programs can legitimately be run on object files built for architectures other than the system they're running on. Thanks! --Will. On Wed, Sep 17, 2014 at 5:01 PM, Will Andrews wrote: > Hi, > > I see there have been a lot of updates & fixes to elftoolchain since > the last import into FreeBSD/head nearly 8 months ago. Are there any > plans to update the import? > > I'm asking because it appears that ctfconvert currently crashes > (specifically, due to a bug in dwarf_attrval_unsigned()), if you try > to use it on C++ object files. > > This is easily demonstrated by applying this patch to FreeBSD/head and > building sbin/devd with WITH_CTF=1: > http://people.freebsd.org/~will/add-ctfconvert-to-cpp-object-files.diff > > Justin Gibbs (cc'd) posted about this issue in February, and it's > still a problem: > http://lists.freebsd.org/pipermail/freebsd-toolchain/2014-February/001121.html > > Thanks, > --Will.