From: Masaki Muranaka <monaka@monami-software.com>
To: Michael Eager <eager@eagercon.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
Michael Eager <eager@eagerm.com>,
gdb-patches@sourceware.org
Subject: Re: [patch] target triplet for Microblaze.
Date: Sat, 04 Dec 2010 02:12:00 -0000 [thread overview]
Message-ID: <3C0393B9-03FB-44AA-BECF-853A409F2556@monami-software.com> (raw)
In-Reply-To: <4CE5AE58.6090506@eagercon.com>
Hello,
Patch applied. Thanks.
On 2010/11/19, at 7:53, Michael Eager wrote:
> Joel Brobecker wrote:
>>>> Also, `microblaze*-linux-*' is there to allow "microblaze-linux-gnu".
>>>> I'm not sure this is really kosher or not. I would think not (we're in
>>>> danger of thinking that the OS name is "gnu" rather than "linux". But
>>>> keeping it if needed shouldn't be too much of a burden as long as this
>>>> is limited to configure.tgt.
>>> Perhaps this would be better as "microblaze*-*-linux" like other targets.
>> I agree this would be better, especially if you think that this is not
>> going to be a problem for existing users. We should even merge it
>> with Masaki's suggestion and make it "microblaze*-*-linux*".
>
> OK with me.
>
> --
> Michael Eager eager@eagercon.com
> 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
>
prev parent reply other threads:[~2010-12-04 2:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 9:23 Masaki Muranaka
2010-11-18 17:10 ` Joel Brobecker
2010-11-18 17:44 ` Michael Eager
2010-11-18 18:14 ` Pedro Alves
2010-11-18 18:44 ` Michael Eager
2010-11-18 20:45 ` Pedro Alves
2010-11-18 21:35 ` Michael Eager
2010-11-18 21:49 ` Pedro Alves
2010-11-18 22:32 ` Joel Brobecker
2010-11-18 22:53 ` Michael Eager
2010-12-04 2:12 ` Masaki Muranaka [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=3C0393B9-03FB-44AA-BECF-853A409F2556@monami-software.com \
--to=monaka@monami-software.com \
--cc=brobecker@adacore.com \
--cc=eager@eagercon.com \
--cc=eager@eagerm.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).