public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: hubicka@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 39f20a091674eb7141d4a15e9a170726e24bce83 Date: Thu, 23 Jan 2020 13:46:00 -0000 [thread overview] Message-ID: <20200123134604.24916.qmail@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 39f20a091674eb7141d4a15e9a170726e24bce83 (commit) from e2c8d26d66e9e7ed7cac2b0aa8a890751329c1c0 (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 39f20a091674eb7141d4a15e9a170726e24bce83 Author: Jan Hubicka <hubicka@ucw.cz> Date: Thu Jan 23 14:45:53 2020 +0100 Fix typo. diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html index 36eb43c..6c6588a 100644 --- a/htdocs/gcc-10/changes.html +++ b/htdocs/gcc-10/changes.html @@ -89,7 +89,7 @@ a work-in-progress.</p> <li><a href="https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/Optimize-Options.html#index-finline-functions"><code>-finline-functions</code></a> is now enabled at <code>-O2</code> and was retuned for better code size versus runtime performance trade-offs. Inliner heuristics was - also significantly sped up to avoid negativive impact to <code>-flto + also significantly sped up to avoid negative impact to <code>-flto -O2</code> compile times. </li> <li>Inliner heuristics and function clonning can now use value-range ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-10/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-01-23 13:46 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=20200123134604.24916.qmail@sourceware.org \ --to=hubicka@gcc.gnu.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: linkBe 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).