Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz), deuling@de.ibm.com (Markus Deuling)
Cc: gdb-patches@sourceware.org (GDB Patches)
Subject: Re: [rfc] Wrap addresses in spu-gdb
Date: Wed, 08 Aug 2007 14:12:00 -0000	[thread overview]
Message-ID: <200708081411.l78EBqII022771@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070808114237.GA27165@caradoc.them.org> from "Daniel Jacobowitz" at Aug 08, 2007 07:42:37 AM

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 ...

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2007-08-08 14:12 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 [this message]
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
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=200708081411.l78EBqII022771@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=deuling@de.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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