Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: Document i386 target features
Date: Mon, 08 Feb 2010 18:38:00 -0000	[thread overview]
Message-ID: <83d40fefpm.fsf@gnu.org> (raw)
In-Reply-To: <20100208153337.GA25531@lucon.org>

> Date: Mon, 8 Feb 2010 07:33:37 -0800
> From: "H.J. Lu" <hongjiu.lu@intel.com>
> 
> Here is the patch to document i386 target features for i386 XML files
> I checked in.  OK to install?

Thanks, I have a few comments:

> +@cindex target descriptions, I386 features

Index entries are supposed to be mostly in lower case.  Would it be
okay to use "i386" instead of I386 here?

> +targets.  It should contain registers @samp{eax} through @samp{edi}
> +plus @samp{eip} for i386 and @samp{rax} through @samp{r15} plus
> +@samp{rip} for amd64, @samp{eflags}, @samp{cs}, @samp{ss}, @samp{ds},
> +@samp{es}, @samp{fs}, @samp{gs}, registers @samp{st0} through @samp{st7},
> +@samp{fctrl}, @samp{fstat}, @samp{ftag}, @samp{fiseg}, @samp{fioff},
> +@samp{foseg}, @samp{fooff} and @samp{fop}.

This list is very long, and makes the sentence long and hard to
grasp.  I think it would be more palatable as an itemized list, like
so:

 It should contain the following registers:

 @itemize @minus
 @item
 @samp{eax} through @samp{edi} and @samp{eip} for i386
 @item
 @samp{rax} through @samp{r15} plus @samp{rip} for amd64
 @item
 @samp{eflags}
 @item
 @samp{cs}, @samp{ss}, @samp{ds}, @samp{es}, @samp{fs}, @samp{gs}
 ...
 @end itemize

(I grouped related registers together to make the list shorter).

Btw, is it "contain the following registers" or "describe the
following registers"? 

> +They may be i386 or amd64 depending on the target.

Who are "they" here?


  reply	other threads:[~2010-02-08 18:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08 15:33 H.J. Lu
2010-02-08 18:38 ` Eli Zaretskii [this message]
2010-02-08 19:13   ` H.J. Lu
2010-02-08 19:28     ` Eli Zaretskii

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=83d40fefpm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@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