public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. bab0b16e94bb57dbb9292664c218fab879be35ad
Date: Tue,  7 Jul 2020 13:06:22 +0000 (GMT)	[thread overview]
Message-ID: <20200707130622.78D673851C34@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  bab0b16e94bb57dbb9292664c218fab879be35ad (commit)
      from  1fc7bcff402ffd58300db5bec6c2644744c4cee8 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit bab0b16e94bb57dbb9292664c218fab879be35ad
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Mon Jul 6 21:59:04 2020 +0200

    Editorial changes to the LTO section.

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index 0959e4c4..4e5f6139 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -143,17 +143,18 @@ You may also want to check out our
     <ul>
       <li>
         A new binary <a href="https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/lto-dump.html"><code>lto-dump</code></a>
-        has been added.  The program can dump various
-        information about a LTO bytecode object file.
+        has been added. It dumps various information about LTO bytecode
+	object files.
       </li>
       <li>
-	Parallel phase of the LTO can automatically detect a running make's
-	jobserver or can fall back to number of available cores.
+	The parallel phase of the LTO can automatically detect a running
+	make's jobserver or fall back to number of available cores.
       </li>
       <li>
-        The LTO bytecode can be compressed with
+        The LTO bytecode can be compressed with the
         <a href="https://facebook.github.io/zstd/"><code>zstd</code></a>
-        algorithm.  Configure script can automatically detect the <code>zstd</code> support.
+        algorithm.  The configure script automatically detects 
+	zstd support.
       </li>
       <li>Most <code>--param</code> values can now be specified at
 	  translation unit granularity. This includes all parameters controlling

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-10/changes.html | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-07-07 13:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200707130622.78D673851C34@sourceware.org \
    --to=gerald@sourceware.org \
    --cc=gcc-cvs-wwwdocs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).