Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ivo Raisr <ivo.raisr@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Bug 20936 - documentation review
Date: Tue, 31 Jan 2017 21:57:00 -0000	[thread overview]
Message-ID: <11e69644-9e33-b5cc-6740-dccca771b3cd@oracle.com> (raw)
In-Reply-To: <83k29bw8i3.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 619 bytes --]



On 31.1.2017 16:32, Eli Zaretskii wrote:
>> From: Ivo Raisr <ivo.raisr@oracle.com>
>> Date: Tue, 31 Jan 2017 05:47:19 +0100
>>
>> Please can I get a documentation review for the attached patch.
>> The affected documentation files are:
>> gdb/doc/gdb.texinfo
>>
>> The patch has been successfully review by Yao Qi <qiyaoltc@gmail.com>.
>
> Sorry for not responding earlier.
>
> The patch for gdb.texinfo is okay, but I don't see the ChangeLog
> entries.  And what about NEWS?

Thank you for review.
ChangeLog entries are attached.
An entry for gdb/NEWS is also attached (I hope that's what you were 
referring to).
I.

[-- Attachment #2: ChangeLog.doc.entry --]
[-- Type: text/plain, Size: 177 bytes --]

ChangeLog entry:
2017-01-17  Ivo Raisr  <ivo.raisr@oracle.com>

	PR tdep/20936
	* gdb.texinfo: (Standard Target Features): Document SPARC features.
	(Sparc Features): New node.

[-- Attachment #3: ChangeLog.testsuite.entry --]
[-- Type: text/plain, Size: 150 bytes --]

ChangeLog entry:
2017-01-17  Ivo Raisr  <ivo.raisr@oracle.com>

	PR tdep/20936
	* gdb.xml/tdesc-regs.exp: Provide sparc core registers for the tests.

[-- Attachment #4: ChangeLog.entry.tdesc-003 --]
[-- Type: text/plain, Size: 1096 bytes --]

ChangeLog entry:
2017-01-17  Ivo Raisr  <ivo.raisr@oracle.com>

	PR tdep/20936
	Provide and use sparc32 and sparc64 target description XML files.
	* features/sparc/sparc32-cp0.xml, features/sparc/sparc32-cpu.xml,
	features/sparc/sparc32-fpu.xml: New files for sparc 32-bit.
	* features/sparc/sparc64-cp0.xml, features/sparc/sparc64-cpu.xml,
	features/sparc/sparc64-fpu.xml: New files for sparc 64-bit.
	* features/sparc/sparc32-solaris.xml: New file.
	* features/sparc/sparc64-solaris.xml: New file.
	* features/sparc/sparc32-solaris.c: Generated.
	* features/sparc/sparc64-solaris.c: Generated.
	* sparc-tdep.h: Account for differences in target descriptions.
	* sparc-tdep.c (sparc32_register_name): Use target provided registers.
	(sparc32_register_type): Use target provided registers.
	(validate_tdesc_registers): New function.
	(sparc32_gdbarch_init): Use tdesc_has_registers.
	Set pseudoregister functions.
	* sparc64-tdep.c (sparc64_register_name): Use target provided registers.
	(sparc64_register_type): Use target provided registers.
	(sparc64_init_abi): Set pseudoregister functions.

[-- Attachment #5: gdb.NEWS.patch --]
[-- Type: text/x-patch, Size: 271 bytes --]

diff --git a/gdb/NEWS b/gdb/NEWS
index 21e8cd3..b71b1ea 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -47,6 +47,8 @@
      end
    end
 
+* Target descriptions can now describe registers for sparc32 and sparc64.
+
 * New native configurations
 
 FreeBSD/mips			mips*-*-freebsd

  reply	other threads:[~2017-01-31 21:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31  4:47 Ivo Raisr
2017-01-31 15:32 ` Eli Zaretskii
2017-01-31 21:57   ` Ivo Raisr [this message]
2017-02-01  3:33     ` Eli Zaretskii
2017-02-06  7:49       ` Jose E. Marchesi

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=11e69644-9e33-b5cc-6740-dccca771b3cd@oracle.com \
    --to=ivo.raisr@oracle.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