Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, mark.kettenis@xs4all.nl
Subject: Re: PATCH: Cache types from target description
Date: Tue, 09 Feb 2010 18:56:00 -0000	[thread overview]
Message-ID: <6dc9ffc81002091056j7dec9db3peddbeae88383316c@mail.gmail.com> (raw)
In-Reply-To: <834olqdz66.fsf@gnu.org>

On Tue, Feb 9, 2010 at 10:47 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Tue, 9 Feb 2010 07:45:13 -0800
>> From: "H.J. Lu" <hongjiu.lu@intel.com>
>> Cc: GDB <gdb-patches@sourceware.org>,         Mark Kettenis <mark.kettenis@xs4all.nl>
>>
>> Here is the updated patch. I fixed i386_eflags and documented them.
>> OK to install?
>
> The doco part is okay, but please fix the following 2 minor issues
> before committing:
>
>> 2010-02-09  H.J. Lu  <hongjiu.lu@intel.com>
>>
>>       * gdb.texinfo: Add i387_ext, i386_eflags and i386_mxcsr.
>
> Please state the name of the node in which you are making the change
> (in parens, as if it were a function).  You can find it by looking
> back from the locus of the change for a line that begins with
> "@node".
>
>> +@item i386_eflags
>> +32bit EFLAGS register used by x86.
>> +
>> +@item i386_mxcsr
>> +32bit MXCSR register used by x86.
>
> It would look prettier in print if you use @sc{eflags} and @sc{mxcsr}
> instead of up-casing them in the Texinfo sources.
>

This is the doc patch I am checking in. I will wait for OK on the other part.

Thanks.


-- 
H.J.
---
2010-02-09  H.J. Lu  <hongjiu.lu@intel.com>

	* gdb.texinfo (Predefined Target Types): Add i387_ext,
	i386_eflags and i386_mxcsr.

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index b31cfed..81c0b6b 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -32749,6 +32749,15 @@ Double precision IEEE floating point.
 @item arm_fpa_ext
 The 12-byte extended precision format used by ARM FPA registers.

+@item i387_ext
+The 10-byte extended precision format used by x87 registers.
+
+@item i386_eflags
+32bit @sc{eflags} register used by x86.
+
+@item i386_mxcsr
+32bit @sc{mxcsr} register used by x86.
+
 @end table

 @node Standard Target Features


  reply	other threads:[~2010-02-09 18:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05  1:15 PATCH: PATCH: Add builtin floating point types H.J. Lu
2010-02-07 21:52 ` Mark Kettenis
2010-02-07 22:00   ` H.J. Lu
2010-02-07 22:14     ` Daniel Jacobowitz
2010-02-07 22:25       ` H.J. Lu
2010-02-07 23:03         ` H.J. Lu
2010-02-07 23:08           ` Daniel Jacobowitz
2010-02-08  2:17             ` H.J. Lu
2010-02-08  4:17               ` Daniel Jacobowitz
2010-02-08  5:16                 ` H.J. Lu
2010-02-08 14:14                   ` Daniel Jacobowitz
2010-02-08 14:56                     ` H.J. Lu
2010-02-08 18:56                     ` H.J. Lu
2010-02-08 18:55 ` PATCH: Cache types from target description H.J. Lu
2010-02-09 15:45   ` H.J. Lu
2010-02-09 18:47     ` Eli Zaretskii
2010-02-09 18:56       ` H.J. Lu [this message]
2010-02-10 18:38     ` Daniel Jacobowitz
2010-02-10 20:54       ` Mark Kettenis
2010-02-10 21:01         ` Daniel Jacobowitz

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=6dc9ffc81002091056j7dec9db3peddbeae88383316c@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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