From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25261 invoked by alias); 27 Sep 2018 05:49:41 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 25224 invoked by uid 89); 27 Sep 2018 05:49:38 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,KAM_SHORT,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: jocasta.intra Received: from de.cellform.com (HELO jocasta.intra) (88.217.224.109) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 27 Sep 2018 05:49:36 +0000 Received: from jocasta.intra (localhost [127.0.0.1]) by jocasta.intra (8.15.2/8.15.2/Debian-8) with ESMTPS id w8R5nPBK004731 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 27 Sep 2018 07:49:25 +0200 Received: (from john@localhost) by jocasta.intra (8.15.2/8.15.2/Submit) id w8R5nPAm004730; Thu, 27 Sep 2018 07:49:25 +0200 Date: Thu, 27 Sep 2018 05:49:00 -0000 From: John Darrington To: Simon Marchi Cc: John Darrington , Tom Tromey , gdb-patches@sourceware.org Subject: Re: [PATCH 2/4] Add a dwarf unit type to represent 24 bit values. Message-ID: <20180927054924.e5hgaw4dwdkjezv3@jocasta.intra> References: <20180829141845.26378-1-john@darrington.wattle.id.au> <20180829141845.26378-3-john@darrington.wattle.id.au> <878t4dvuyf.fsf@tromey.com> <20180926174157.mw5eocxlfmgliua7@jocasta.intra> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) X-SW-Source: 2018-09/txt/msg00868.txt.bz2 On Wed, Sep 26, 2018 at 10:53:34PM -0400, Simon Marchi wrote: On 2018-09-26 13:41, John Darrington wrote: > After discussion with the gcc folks, it seems that there is an easier > and much simpler solution, which I'm attaching. > > J' Err can you explain how this works, or link to the gcc discussion if it's explained there? I must be missing something, because as far as I understand, this will read 4 bytes when reading an address, when I suppose it's encoded with 3 bytes in the DWARF info, isn't it? Simon The relevant discussion is here: https://gcc.gnu.org/ml/gcc-patches/2018-09/msg00712.html The bottom line is that the dwarf address size does not need to correspond to the machine address size (and in general it does not) - it just needs to be at least as long. J' -- Avoid eavesdropping. Send strong encrypted email. PGP Public key ID: 1024D/2DE827B3 fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 See http://sks-keyservers.net or any PGP keyserver for public key.