From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: lgustavo@codesourcery.com
Cc: palves@redhat.com (Pedro Alves), tromey@redhat.com (Tom Tromey),
stanshebs@earthlink.net (Stan Shebs),
gdb-patches@sourceware.org (GDB Patches)
Subject: Re: [PATCH, testsuite] Don't run SREC, IHEX and TEKHEX tests for MIPS N64.
Date: Thu, 04 Jul 2013 13:22:00 -0000 [thread overview]
Message-ID: <201307041322.r64DMeIf026838@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <51D47A05.9020404@codesourcery.com> from "Luis Machado" at Jul 03, 2013 04:22:45 PM
Luis Machado wrote:
> On 07/03/2013 12:05 PM, Pedro Alves wrote:
> > On 07/02/2013 07:50 PM, Luis Machado wrote:
> >> -
> >> -if {[istarget "spu*-*-*"]} then {
> >> - # The internal address format used for the combined Cell/B.E.
> >> - # debugger requires 64-bit.
> >> - set is64bitonly "yes"
> >> -}
> >> -
> >
> > I'm not sure this equates to sizeof pointer == 64-bit.
> > This bit may need to be retained. [Adding Ulrich].
>
> Fair enough. Ulrich, let me know if the pointer check in the attached
> patch doesn't make sense for Cell BE.
No, the pointer check is not enough. The problem is that on Cell/B.E.,
GDB uses a (purely internal to GDB) address format to encode multiple
address spaces into a synthetic GDB address space. See the long
comment in spu-tdep.h for details.
The "restore" command needs a full internal 64-bit address on Cell/B.E.
to uniquely identify the location where to restore memory. Thus using
a data format that can only remember 32-bit addresses don't work:
http://sourceware.org/ml/gdb-patches/2008-09/msg00139.html
However, just testing the size of a pointer will return 32-bit on SPU,
because that's the ABI-defined pointer size (the 64 bits are purely
GDB internal). So I think Cell/B.E. / SPU will need to remain a
special case here for now.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2013-07-04 13:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 16:24 Luis Machado
2013-07-02 14:37 ` Yao Qi
2013-07-02 14:45 ` Luis Machado
2013-07-03 0:03 ` Yao Qi
2013-07-02 16:47 ` Tom Tromey
2013-07-02 16:51 ` Luis Machado
2013-07-02 17:19 ` Stan Shebs
2013-07-02 18:10 ` Tom Tromey
2013-07-02 18:50 ` Luis Machado
2013-07-02 20:55 ` Tom Tromey
2013-07-03 15:05 ` Pedro Alves
2013-07-03 19:23 ` Luis Machado
2013-07-03 19:26 ` Pedro Alves
2013-07-03 20:19 ` Luis Machado
2013-07-04 8:11 ` Pedro Alves
2013-07-06 2:41 ` Luis Machado
2013-07-03 20:35 ` Maciej W. Rozycki
2013-07-03 20:54 ` Luis Machado
2013-07-03 21:08 ` Maciej W. Rozycki
2013-07-04 11:48 ` Luis Machado
2013-07-04 12:13 ` Maciej W. Rozycki
2013-07-04 12:21 ` Luis Machado
2013-07-04 13:22 ` Ulrich Weigand [this message]
2013-07-04 13:24 ` Luis Machado
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=201307041322.r64DMeIf026838@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=palves@redhat.com \
--cc=stanshebs@earthlink.net \
--cc=tromey@redhat.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