public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Pierre-Marie de Rodat <derodat@adacore.com>
To: "Sivanupandi, Pitchumani" <Pitchumani.Sivanupandi@atmel.com>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Cc: Andrew Burgess <andrew.burgess@embecosm.com>,
	"tom@tromey.com" <tom@tromey.com>,
	"uweigand@de.ibm.com" <uweigand@de.ibm.com>
Subject: Re: dynamic array's upper bound evaluated as address for AVR target
Date: Wed, 14 Oct 2015 06:54:00 -0000	[thread overview]
Message-ID: <561DFC25.5020106@adacore.com> (raw)
In-Reply-To: <CAC140656783604CABA6AE60C2A6D5A4A2ED2398@penmbx01>

On 10/14/2015 08:32 AM, Sivanupandi, Pitchumani wrote:
> Target hook for integer_to_address does some manipulation on the given value.
> In AVR target, it adds SRAM memory mask to the value to make that SRAM address.

This is what I observed, but I wonder: why do we need this in the first 
place? In what situation do we have an integer on which we need to apply 
a mask to get an address (i.e. from where does this integer come?).

> Function dwarf2_locexpr_baton_eval is called by dwarf2_evaluate_property for
> location expression (from resolve_dynamic_range. i.e. to resolve bounds of
> dynamic array e.g. int int_vla[n] where n is function parameter).

Then maybe we should add this expect_address parameter to both 
dwarf2_evaluate_property and dwarf2_locexpr_baton_eval…

-- 
Pierre-Marie de Rodat

  reply	other threads:[~2015-10-14  6:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13  9:08 Sivanupandi, Pitchumani
2015-10-13 14:44 ` Pierre-Marie de Rodat
2015-10-14  6:33   ` Sivanupandi, Pitchumani
2015-10-14  6:54     ` Pierre-Marie de Rodat [this message]
2015-10-14  7:54       ` Sivanupandi, Pitchumani
2015-10-14  8:26         ` Pierre-Marie de Rodat
2015-10-14  9:41           ` Ulrich Weigand
2015-10-14 12:26             ` Joel Brobecker
2015-10-14 13:37               ` Pierre-Marie de Rodat
2015-10-23 14:19                 ` Pierre-Marie de Rodat
2015-10-23 16:47                   ` Ulrich Weigand
2015-10-14 10:15           ` Sivanupandi, Pitchumani
2015-10-14 13:39             ` Pierre-Marie de Rodat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=561DFC25.5020106@adacore.com \
    --to=derodat@adacore.com \
    --cc=Pitchumani.Sivanupandi@atmel.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb@sourceware.org \
    --cc=tom@tromey.com \
    --cc=uweigand@de.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).