This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [rfc] Wrap addresses in spu-gdb
- From: Daniel Jacobowitz <drow at false dot org>
- To: Markus Deuling <deuling at de dot ibm dot com>
- Cc: Ulrich Weigand <uweigand at de dot ibm dot com>, Jim Blandy <jimb at codesourcery dot com>, GDB Patches <gdb-patches at sourceware dot org>
- Date: Tue, 21 Aug 2007 07:14:32 -0400
- Subject: Re: [rfc] Wrap addresses in spu-gdb
- References: <200708201842.l7KIg16S028544@d12av02.megacenter.de.ibm.com> <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