Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Yao Qi <yao@codesourcery.com>
Subject: Re: [RFA 5/8] New port: TI C6x: gdb port
Date: Wed, 10 Aug 2011 13:44:00 -0000	[thread overview]
Message-ID: <201108101444.36843.pedro@codesourcery.com> (raw)
In-Reply-To: <4E41EEB3.8040400@codesourcery.com>

On Wednesday 10 August 2011 03:36:35, Yao Qi wrote:
> On 08/09/2011 11:41 PM, Pedro Alves wrote:
> >>> > > 
> >>> > > You can't do that given the descriptions specify GNU/Linux osabi.
> >>> > > There should be linux, and non-linux variants.
> >>> > > 
> >> > 
> >> > Can't we get rid of osabi from xml description, and use them both for
> >> > linux and non-linux?  Similar to arm's target descriptions.
> > We can, but that's a bit a step backwards.  arm's descriptions don't
> > set the osabi because the support for the osabi field element was added
> > after the descriptions were.  Having the target tell gdb the osabi makes
> > a multi-target gdb (*) figure out the correct arch even if you don't
> > specify an executable (for attach).
> 
> I see, thanks for the explanation, Pedro.
> 
> > I believe that with an xi:include, the linux xml file would be minimal.
> 
> I reference the i386 xml files, and do the similar for tic6x.  Copy
> tic6x-{c62x,c64x,c64xp}.xml to tic6x-{c62x,c64x,c64xp}-linux.xml, and
> add osabi in tic6x-*-linux.xml files.  Generate corresponding *.c files
> and *.data files.

Thanks, sounds good.

> In the new patch, linux target descriptions are initialized in
> tic6x-linux-tdep.c:_initialize_tic6x_linux_tdep, and non-linux target
> descriptions are initialized in tic6x-tdep.c:_initialize_tic6x_tdep.

Patch looks good to me.

-- 
Pedro Alves


      reply	other threads:[~2011-08-10 13:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20  2:10 Yao Qi
2011-07-25 11:32 ` Yao Qi
2011-08-03  1:15   ` ping: " Yao Qi
2011-08-04 12:34 ` Pedro Alves
2011-08-04 15:11   ` Joseph S. Myers
2011-08-04 17:45     ` Pedro Alves
2011-08-04 19:48       ` Joseph S. Myers
2011-08-05  2:13       ` Yao Qi
2011-08-06  2:26   ` Yao Qi
2011-08-08 13:04     ` Pedro Alves
2011-08-09  2:52       ` Yao Qi
2011-08-09 14:01         ` Pedro Alves
2011-08-09 15:16           ` Yao Qi
2011-08-09 15:42             ` Pedro Alves
2011-08-10  2:37               ` Yao Qi
2011-08-10 13:44                 ` Pedro Alves [this message]

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=201108101444.36843.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.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