From: Jim Blandy <jimb@codesourcery.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: drow@false.org (Daniel Jacobowitz),
deuling@de.ibm.com (Markus Deuling),
gdb-patches@sourceware.org (GDB Patches)
Subject: Re: [rfc] Wrap addresses in spu-gdb
Date: Wed, 08 Aug 2007 17:10:00 -0000 [thread overview]
Message-ID: <m3y7gmhrzj.fsf@codesourcery.com> (raw)
In-Reply-To: <200708081411.l78EBqII022771@d12av02.megacenter.de.ibm.com> (Ulrich Weigand's message of "Wed, 8 Aug 2007 16:11:51 +0200 (CEST)")
"Ulrich Weigand" <uweigand@de.ibm.com> writes:
> Daniel Jacobowitz wrote:
>> On Wed, Aug 08, 2007 at 08:44:29AM +0200, Markus Deuling wrote:
>> > + if (target_has_registers && target_has_stack && target_has_memory
>> > + /* FIXME: Currently needed for dwarf2_read_address to work. */
>> > + && type != builtin_type_uint32)
>>
>> I think that you shouldn't commit a patch with this hack in it.
>> It looks very fragile.
>
> Agreed. Markus, this is a special hack for the combined PPE/SPE
> debugger, it shouldn't be necessary for the SPU-standalone (and
> mainline) version.
>
> I'll have to look into fixing the underlying issue cleanly when
> merging the combined debugger ...
There seem to be a number of cases where conversions between addresses
and pointers require live values from other registers --- for example,
when a pointer's bits are augmented with bits from some system
register, like a segment base register. I'd want to work in the
context of real-world examples, but it might be a good idea to
introduce frame_and_pointer_to_address and
frame_and_address_to_pointer, and use them where they make sense.
Using such functions, clipping SPE addresses using the LSLR register
could be carried out in a reasonable way.
next prev parent reply other threads:[~2007-08-08 17:10 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 [this message]
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
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=m3y7gmhrzj.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=deuling@de.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--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