From: Jiong Wang <jiwang@tilera.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH] mention tilegx in gdb 7.6 release news
Date: Mon, 01 Apr 2013 12:54:00 -0000 [thread overview]
Message-ID: <51598054.7060207@tilera.com> (raw)
In-Reply-To: <514A6931.3030400@tilera.com>
on 2013/3/21 9:58, Jiong Wang wrote:
>
>>>
>>> gdb/ChangeLog:
>>>
>>> * NEWS: mention TILE-Gx in "New native configurations" and
>>> "New targets" section.
>>>
>>> please CR, thanks.
>> JIC: If this patch gets approved, it needs to be ported to the 7.6
>> branch as well.
>
> Got it. So, this patch approved?
Ping.
---
Regards,
Jiong
Tilera Corporation
>
> ---
> Regards,
> Jiong
> Tilera Corporation
>
>>
>> Thank you!
>>
>>> ---
>>> Regards,
>>> Jiong
>>>
>>>
>>>> ---
>>>> Regards,
>>>> Jiong
>>>> Tilera Corporation.
>>> diff --git a/gdb/NEWS b/gdb/NEWS
>>> index b759adf..e3f544e 100644
>>> --- a/gdb/NEWS
>>> +++ b/gdb/NEWS
>>> @@ -47,6 +47,7 @@ record function-call-history prints the
>>> execution history at
>>> ARM AArch64 GNU/Linux aarch64*-*-linux-gnu
>>> FreeBSD/powerpc powerpc*-*-freebsd
>>> +Tilera TILE-Gx GNU/Linux tilegx*-*-linux-gnu
>>> * New targets
>>> @@ -54,6 +55,7 @@ ARM AArch64 aarch64*-*-elf
>>> ARM AArch64 GNU/Linux aarch64*-*-linux
>>> Lynx 178 PowerPC powerpc-*-lynx*178
>>> x86_64/Cygwin x86_64-*-cygwin*
>>> +Tilera TILE-Gx GNU/Linux tilegx*-*-linux
>>> * If the configured location of system.gdbinit file (as given by
>>> the
>>> --with-system-gdbinit option at configure time) is in the
>>
>
next prev parent reply other threads:[~2013-04-01 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 12:40 Jiong Wang
2013-03-14 12:59 ` Jiong Wang
2013-03-20 16:00 ` Joel Brobecker
2013-03-21 3:50 ` Jiong Wang
2013-04-01 12:54 ` Jiong Wang [this message]
2013-04-01 18:14 ` Eli Zaretskii
2013-04-02 13:39 ` [COMMITTED][PATCH] " Jiong Wang
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=51598054.7060207@tilera.com \
--to=jiwang@tilera.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--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