Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yan-Ting Lin <currygt52@gmail.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org, eliz@gnu.org
Subject: Re: [PATCH v2] AndesTech NDS32 port
Date: Fri, 17 Jun 2016 08:08:00 -0000	[thread overview]
Message-ID: <a74afdc0-1eb0-9db8-4cd9-a490893dbc06@gmail.com> (raw)
In-Reply-To: <8660tlvwqy.fsf@gmail.com>

Yao Qi 於 2016/6/7 下午 11:34 寫道:
> Patch except doc and news bits is good to me.  Doc and NEWS bits should
> be reviewed by Eli.
> 
> If there is no other comments in one week, you can push it in.
> 

Hi GDB maintainers and reviewers,

I will push our patch in after rebasing it to the latest code.

Here is the ChangeLog entries I will push in.
Thanks again for your help.

ChangeLog entries:

gdb/:
2016-06-17  Yan-Ting Lin  <currygt52@gmail.com>

	* Makefile.in (ALL_TARGET_OBS): Add nds32-tdep.o.
	(HFILES_NO_SRCDIR): Add nds32-tdep.h.
	(ALLDEPFILES): Add nds32-tdep.c.
	* NEWS: Mention new NDS32 port.
	* configure.tgt: Add NDS32.
	* nds32-tdep.c: New file.
	* nds32-tdep.h: New file.
	* features/Makefile (XMLTOC): Add nds32.xml.
	* features/nds32-core.xml: New file.
	* features/nds32-fpu.xml: New file.
	* features/nds32-system.xml: New file.
	* features/nds32.c: New file (generated).
	* features/nds32.xml: New file.

gdb/testsuite/:
2016-06-17  Yan-Ting Lin  <currygt52@gmail.com>

	* gdb.base/float.exp: Add target check for nds32*-*-*.
	* gdb.xml/tdesc-regs.exp: Set core-regs for nds32*-*-*.

gdb/doc/:
2016-06-17  Yan-Ting Lin  <currygt52@gmail.com>

	* gdb.texinfo (Standard Target Features): Document NDS32 features.
	(NDS32 Features): New Section.


  parent reply	other threads:[~2016-06-17  8:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-05  7:16 Yan-Ting Lin
2016-05-05 23:46 ` Kevin Buettner
2016-05-06 11:00   ` Yao Qi
2016-05-06 16:09     ` Kevin Buettner
2016-05-09  8:15 ` Yao Qi
2016-05-10  8:45   ` Yan-Ting Lin
2016-05-09 18:33 ` Pedro Alves
2016-05-10  9:31   ` Yan-Ting Lin
2016-05-15  9:39   ` Yan-Ting Lin
2016-06-01 11:28     ` Yao Qi
2016-06-06 15:13       ` Yan-Ting Lin
2016-06-07 15:34         ` Yao Qi
2016-06-07 16:30           ` Eli Zaretskii
2016-06-08  8:17             ` Yao Qi
2016-06-17  8:08           ` Yan-Ting Lin [this message]
2016-06-13 14:12         ` Pedro Alves
2016-06-15  8:44           ` Yan-Ting Lin
2016-06-15 10:07             ` Pedro Alves
2016-06-01 10:52 ` Yao Qi
2016-06-01 11:00   ` Yao Qi

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=a74afdc0-1eb0-9db8-4cd9-a490893dbc06@gmail.com \
    --to=currygt52@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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