From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9707 invoked by alias); 3 Mar 2003 11:26:16 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 9699 invoked from network); 3 Mar 2003 11:26:13 -0000 Received: from unknown (HELO fw-cam.cambridge.arm.com) (193.131.176.3) by 172.16.49.205 with SMTP; 3 Mar 2003 11:26:13 -0000 Received: by fw-cam.cambridge.arm.com; id LAA09709; Mon, 3 Mar 2003 11:26:08 GMT Received: from unknown(172.16.1.2) by fw-cam.cambridge.arm.com via smap (V5.5) id xma008979; Mon, 3 Mar 03 11:25:26 GMT Received: from pc960.cambridge.arm.com (pc960.cambridge.arm.com [10.1.205.4]) by cam-admin0.cambridge.arm.com (8.9.3/8.9.3) with ESMTP id LAA11918; Mon, 3 Mar 2003 11:25:18 GMT Received: from pc960.cambridge.arm.com (rearnsha@localhost) by pc960.cambridge.arm.com (8.11.6/8.9.3) with ESMTP id h23BPKW06819; Mon, 3 Mar 2003 11:25:20 GMT Message-Id: <200303031125.h23BPKW06819@pc960.cambridge.arm.com> X-Authentication-Warning: pc960.cambridge.arm.com: rearnsha owned process doing -bs To: Daniel Jacobowitz cc: Andrew Cagney , Mark Kettenis , brobecker@gnat.com, mec@shout.net, gdb@sources.redhat.com, Richard.Earnshaw@arm.com Reply-To: Richard.Earnshaw@arm.com Organization: ARM Ltd. X-Telephone: +44 1223 400569 (direct+voicemail), +44 1223 400400 (switchbd) X-Fax: +44 1223 400410 X-Address: ARM Ltd., 110 Fulbourn Road, Cherry Hinton, Cambridge CB1 9NJ. Subject: Re: 8-byte register values on a 32-bit machine In-reply-to: Your message of "Sat, 01 Mar 2003 19:28:00 EST." <20030302002759.GA12252@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Mar 2003 11:26:00 -0000 From: Richard Earnshaw X-SW-Source: 2003-03/txt/msg00045.txt.bz2 > On Sat, Mar 01, 2003 at 06:42:58PM -0500, Andrew Cagney wrote: > > Mark, > > > > Now that there is this loc_computed stuff, it is probably possible to > > modify stabs to, for the case in question, implement a loc_computed symbol. > > Hmm, I'm not sure that's the right way to go. DWARF-2 also will say > that an eight byte value is in one register. Why put the hacks in > both readers? > > By the way, assuming I can find the time (ugh) I'm not done with > LOC_COMPUTED yet. On my list so far: > - Location lists > - Turning locations into better defined objects > - Thus, allowing LOC_COMPUTED to return a non-computed "location" > - Allowing more complex locations, namely DW_OP_piece style. > - Eventually turning on more uses of DW_OP_piece in GCC. The main reason gcc allocates objects to contiguous register ranges is because gdb can't handle anything else. Fixing gdb to allow location lists would be a major step forward, since then gcc would be able to split double-register objects before register allocation and allocate each part individually. That could be a major win on register starved machines. R.