From: Daniel Jacobowitz <drow@false.org>
To: Markus Deuling <deuling@de.ibm.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
Jim Blandy <jimb@codesourcery.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [rfc] Wrap addresses in spu-gdb
Date: Tue, 21 Aug 2007 11:14:00 -0000 [thread overview]
Message-ID: <20070821111432.GA19013@caradoc.them.org> (raw)
In-Reply-To: <46CAB6B7.30806@de.ibm.com>
On Tue, Aug 21, 2007 at 11:56:07AM +0200, Markus Deuling wrote:
> So there are three issues:
>
> 1) Should add-symbol-file set the function address to -in this case- 0x0 ?
> SPU hardware would handle both 0x40000 and 0x80000 as 0x0.
I don't know the answer to this one, but the current behavior is
definitely strange. My guess is that something has wrapped the values
to zero and decided that meant unspecified.
> 2) As seen in my example "add-symbol-file" loads two functions to the same
> addresses 0x100.
> Is this valid?
Yes.
> 3) Should the used addresses in the testcase be changed to, for example,
> 0x10000 and 0x20000? This would work for SPU, too. Or shall I introduce
> variables for this addresses and set them to a range < SPU_LS_SIZE for
> SPU targets only?
I think changing the addresses is fine.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-08-21 11:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 6:46 Markus Deuling
2007-08-08 11:42 ` Daniel Jacobowitz
2007-08-08 14:12 ` Ulrich Weigand
2007-08-08 17:10 ` Jim Blandy
2007-08-09 10:39 ` Markus Deuling
2007-08-20 18:42 ` Ulrich Weigand
2007-08-21 9:57 ` Markus Deuling
2007-08-21 11:14 ` Daniel Jacobowitz [this message]
2007-08-27 13:01 ` Markus Deuling
2007-08-27 14:32 ` Ulrich Weigand
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=20070821111432.GA19013@caradoc.them.org \
--to=drow@false.org \
--cc=deuling@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.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