Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Jeff Kenton <jkenton@tilera.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add support for Tilera TILE-Gx processor (part 1/2: gdb)
Date: Tue, 24 Apr 2012 22:40:00 -0000	[thread overview]
Message-ID: <4F971DF6.6020402@redhat.com> (raw)
In-Reply-To: <4F970A44.8060109@tilera.com>

On 04/24/2012 09:17 PM, Jeff Kenton wrote:

> On 04/24/2012 12:14 PM, Pedro Alves wrote:
>> Could you please split the series further one more time (and resubmit as a new thread, not as a reply to this one)? I'd like to see the host-independent tdep bits split out from the linux native debugger support (the nat bits). So you'll end up with 3 patches (you should be able to debug against gdbserver with just the tdep bits, and the gdbserver bits, for example.). That'll make it easier to see such issues and what else might need adjustment to current GDB's way of doing things. 
> 
> Hi Pedro,
> 
> Could you clarify this for me please.


> Are you asking me to re-distribute the existing files I submitted among 3 patches?

This.

Don't think in terms of files.  Think in terms of logical pieces.
There are 3 logical pieces to your patches.

 1 - gdb port base support for TILE-Gx.  The tdep files (unwinder, etc.), and associated
     glue.  These are host independent bits (can be compiled and used by a gdb running
     on any of the supported hosts.  E.g., a Windows gdb should be able to connect and debug
     tile target).  Generic TILE-Gx bits should be in tilegx-tdep.c, and GNU/Linux specific
     bits should be in a tilegx-linux-tdep.c file.
 2 - The GNU/Linux native port (the tilegx-linux-nat.c file and associated glue).  These files
     are only built when building a native gdb that will run on TILE-Gx machines.
 3 - The GNU/Linux gdbserver port.

Your patch currently mixes 1 and 2 together.  2 and 3 are similar in nature, although
the implementations are naturally a bit different given the different codebases.
E.g., with just patches 1 and 3, discarding 2, you should be able to debug a tile
target running gdbserver, connecting from a gdb running on a x86 host (with
gdb configured with --target=tile-unknown-linux-gnu) (if TILE-Gx is big endian, that'd
be a good test to flush out host-independence issues from patch 1).

-- 
Pedro Alves


  reply	other threads:[~2012-04-24 21:41 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 19:26 Jeff Kenton
2012-04-20  1:58 ` Yao Qi
2012-04-20 12:54 ` Joel Brobecker
2012-04-20 14:03   ` Jeff Kenton
2012-04-21  0:34     ` Joel Brobecker
2012-04-23 19:59   ` Jeff Kenton
2012-04-24 16:07     ` Pedro Alves
2012-04-24 16:07     ` Pedro Alves
2012-04-24 16:07     ` Pedro Alves
2012-04-24 16:07     ` Pedro Alves
2012-04-24 16:08     ` Pedro Alves
2012-04-24 16:11     ` Pedro Alves
2012-04-24 16:14     ` Pedro Alves
2012-04-24 16:22     ` Pedro Alves
2012-04-24 18:47       ` Jeff Kenton
2012-04-24 20:21       ` Jeff Kenton
2012-04-24 22:40         ` Pedro Alves [this message]
2012-04-24 16:23     ` Pedro Alves
2012-04-24 16:27     ` Pedro Alves
2012-04-24 16:38     ` Pedro Alves
2012-04-24 16:40     ` Pedro Alves
2012-04-24 16:41       ` Pedro Alves
2012-04-24 16:41     ` Pedro Alves
2012-04-24 16:59       ` Jeff Kenton
2012-04-24 16:42     ` Pedro Alves
2012-04-24 16:54     ` Pedro Alves
2012-04-25  2:18     ` Yao Qi
2012-04-23 20:12   ` [PATCH] Add support for Tilera TILE-Gx processor (part 2/2: gdbserver) Jeff Kenton
2012-04-24 16:54     ` Pedro Alves
2012-04-24 16:55     ` Pedro Alves
2012-04-24 17:34     ` Pedro Alves
2012-05-03 14:28       ` Jeff Kenton
2012-05-03 14:44         ` Pedro Alves

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=4F971DF6.6020402@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jkenton@tilera.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