public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 08249747b2539776f2f071438e6c496e174bfcfc Date: Mon, 26 Apr 2021 20:25:35 +0000 (GMT) [thread overview] Message-ID: <20210426202535.DB11738930EC@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 08249747b2539776f2f071438e6c496e174bfcfc (commit) from c88fea4535093106bb9dcb1548194e1d94b0bd2a (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 08249747b2539776f2f071438e6c496e174bfcfc Author: Jan Hubicka <hubicka@ucw.cz> Date: Mon Apr 26 22:25:18 2021 +0200 Document IPA/LTO/FDO changes. diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index 6f58cfe8..2c98b9a3 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -170,6 +170,39 @@ a work-in-progress.</p> use <code>-g</code> together with <code>-gdwarf-2</code>, <code>-gdwarf-3</code> or <code>-gdwarf-4</code>. </li> + <li> + Inter-procedural optimization improvements: + <ul> + <li>A new IPA-modref pass was added to track side effects of function calls + and improve precision of points-to-analysis. The pass can be controlled + by the <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Optimize-Options.html#index-fipa-modref"><code>-fipa-modref</code></a> option. + </li> + <li>The identical code folding pass (controlled by <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Optimize-Options.html#index-fipa-ocf"><code>-fipa-icf</code></a>) + was significantly improved to increase the number of + unified functions and to reduce compile-time memory use.</li> + <li>IPA-CP (Interprocedural constant propagation) + heuristics improved its estimation of potential usefulness of + known loop bounds and strides by taking the estimated frequency of + these loops into account.</li> + </li> + <li> + Link-time optimization improvements: + <ul> + <li>The LTO bytecode format was optimized for smaller object files and + faster streaming.</li> + <li>Memory allocation of the linking stage was improved to reduce peak + memory use.</li> + </ul> + </li> + <li> + Profile driven optimization improvements: + <ul> + <li> + Using <a href="https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gcc/Optimize-Options.html#index-fprofile-values"><code>-fprofile-values</code></a>, + was improved by tracking more target values for e.g. indirect calls. + </li> + </ul> + </li> </ul> <!-- .................................................................. --> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/changes.html | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-04-26 20:25 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=20210426202535.DB11738930EC@sourceware.org \ --to=hubicka@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: 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).