From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 121454 invoked by alias); 14 Oct 2015 12:26:47 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 121443 invoked by uid 89); 14 Oct 2015 12:26:46 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Wed, 14 Oct 2015 12:26:45 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 34CD829661; Wed, 14 Oct 2015 08:26:43 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 7Nhsat8z-B0j; Wed, 14 Oct 2015 08:26:43 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 4936A29268; Wed, 14 Oct 2015 08:26:40 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id AA2B542BBA; Wed, 14 Oct 2015 05:26:38 -0700 (PDT) Date: Wed, 14 Oct 2015 12:26:00 -0000 From: Joel Brobecker To: Ulrich Weigand Cc: Pierre-Marie de Rodat , Sivanupandi Pitchumani , "gdb@sourceware.org" , Andrew Burgess , "tom@tromey.com" Subject: Re: dynamic array's upper bound evaluated as address for AVR target Message-ID: <20151014122638.GG661@adacore.com> References: <561E11A2.5030206@adacore.com> <20151014094141.54C93DAD@oc7340732750.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151014094141.54C93DAD@oc7340732750.ibm.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2015-10/txt/msg00069.txt.bz2 > I think the current GDB "dynamic property" mechanism was probably intended > to capture what DWARF section 2.19 specifies, but due to its simultaneous > use for DW_AT_data_location and DW_AT_static_link, things got confused. > > It would probably be best to clearly separate this out into two separate > mechanisms, one that precisely implements dynamic properties as defined > in section 2.19, and one that implements location descriptions. (Note > that those mechanism should ideally then be used for some of the *other* > places where the DWARF standard also allows either a dynamic property or > a location description, but GDB doesn't accept them yet.) > > This would then have the side effect that we could distinguish return > types: location descriptions always return an address, but section 2.19 > dynamic attributes always return an integer. Sounds correct to me. -- Joel