From: Yao Qi <yao@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 5/8] New port: TI C6x: gdb port
Date: Tue, 09 Aug 2011 15:16:00 -0000 [thread overview]
Message-ID: <4E414F30.6050508@codesourcery.com> (raw)
In-Reply-To: <201108091501.31358.pedro@codesourcery.com>
On 08/09/2011 10:01 PM, Pedro Alves wrote:
> On Tuesday 09 August 2011 03:52:13, Yao Qi wrote:
>> Yes, we have target descriptions for tic6x-uclinux, but don't have for
>> tic6x-elf so far. So the target description is initialized in
>> tic6x-linux-tdep.c:_initialize_tic6x_linux_tdep.
>>
>> I think the target description initialization should be moved to
>> tic6x-tdep.c:_initialize_tic6x_tdep, so tic6x-uclinux and tic6x-elf
>> share the target descriptions. In my new patch, target description
>> initialization is moved to tic6x-tdep.c:_initialize_tic6x_tdep, and
>> suffix "-linux" in feature names and files is removed (target
>> description is revised accordingly).
>
> 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.
--
Yao (é½å°§)
next prev parent reply other threads:[~2011-08-09 15:16 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 [this message]
2011-08-09 15:42 ` Pedro Alves
2011-08-10 2:37 ` Yao Qi
2011-08-10 13: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=4E414F30.6050508@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@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