Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Markus Deuling <deuling@de.ibm.com>,
		GDB Patches <gdb-patches@sourceware.org>
Subject: Re: Patch: Add arch_string to spu-low.c
Date: Thu, 22 Feb 2007 15:30:00 -0000	[thread overview]
Message-ID: <20070222153005.GA4563@caradoc.them.org> (raw)
In-Reply-To: <200702221521.l1MFLSBQ013672@d12av02.megacenter.de.ibm.com>

On Thu, Feb 22, 2007 at 04:21:28PM +0100, Ulrich Weigand wrote:
> Daniel Jakowobitz wrote:
> 
> > OK if it's OK with Ulrich (do you always want "SPU:256K"?  Just "spu"
> > should work too).
> 
> Can you elaborate on what effect that change would have?  Does it
> then try to automatically select the subarchitecture?  (We just
> have the one right now anyway ...)

It will select the default subarchitecture - what may be more
interesting is that it won't complain if the user or binary file has
selected a different subarchitecture.  This is a bit tricky; see
choose_architecture_for_target in arch-utils.c, particularly the
the_default check.

So suppose you have in the future an spu:512K, and gdbserver doesn't
need to know the difference, but it's recorded in the ELF file.  GDB
would object if gdbserver reported "I have an spu:256K".

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-02-22 15:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22 14:33 Markus Deuling
2007-02-22 14:56 ` Daniel Jacobowitz
2007-02-22 15:21   ` Ulrich Weigand
2007-02-22 15:30     ` Daniel Jacobowitz [this message]
2007-02-22 15:34       ` Ulrich Weigand
2007-02-22 16:36         ` Markus Deuling
2007-02-22 16:45           ` Daniel Jacobowitz
2007-02-22 17:42             ` Ulrich Weigand
2007-02-22 14:57 Markus Deuling

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=20070222153005.GA4563@caradoc.them.org \
    --to=drow@false.org \
    --cc=deuling@de.ibm.com \
    --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