public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Igor Zamyatin <izamyatin@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Uros Bizjak <ubizjak@gmail.com>
Subject: Re: [GCC 4.8 wwwdocs] PATCH: Mention several user-visible changes for x86
Date: Sun, 17 Feb 2013 23:07:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.00.1302180003480.1859@tuna.site> (raw)
In-Reply-To: <CAKdSQZkm2hfJtVinOseoM9fHyczqXn_OR4mMCW0U+rcz7sgCyA@mail.gmail.com>

On Fri, 15 Feb 2013, Igor Zamyatin wrote:
> Is it ok for wwwdocs?

Index: htdocs/gcc-4.8/changes.html
===================================================================
+     <li>Support for the new Intel processor codename Broadwell with RDSEED,
+     ADCX, ADOX, PREFETCHW is available through <code>-madx</code>,
+     <code>-mprfchw</code>, <code>-mrdseed</code>.

Can you make this <code>RDSEED</code>, <code>... and so forth?
(This is a bit borderline, in that one could also see this as
more general references, but usually we mark those up.)

And "...through the ... command-line options."?

+     <li> Support for Intel RTM and HLE intrinsics, built-in

"the ... intrinsics" (and same below for "instruction sets")

+     <li> x86 backend was improved to allow option
<code>-fscedule-insns</code> to work reliably.

"The x86 backend has been improved..."

+     This option can be used to schedule instructions better and can
lead to improved performace in certain cases.

This line is quite long, can you break lines around 76 columns?

And, let's be a bit more brave and omit either "can" or "in certain
cases".  Otherwise this may sounds too unlikely. :-)

The patch is fine with changes along the lines described above.

Thanks,
Gerald

  reply	other threads:[~2013-02-17 23:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 19:45 [GCC 4.8 changes] " Igor Zamyatin
2013-02-12 19:59 ` Uros Bizjak
2013-02-13 11:17   ` Igor Zamyatin
2013-02-13 11:21     ` Uros Bizjak
2013-02-15 14:16       ` [GCC 4.8 wwwdocs] " Igor Zamyatin
2013-02-17 23:07         ` Gerald Pfeifer [this message]
2013-02-18  6:28           ` Igor Zamyatin
2013-02-20  8:34             ` Kirill Yukhin
     [not found]           ` <13cec1bc4ff.2760.0f39ed3bcad52ef2c88c90062b7714dc@gmail.com>
2013-02-18  7:02             ` Bernhard Reutner-Fischer

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=alpine.LNX.2.00.1302180003480.1859@tuna.site \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=izamyatin@gmail.com \
    --cc=ubizjak@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).