public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Richard Biener <rguenth@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. ae50e86ee44eac14e1fcf291f799c3c8ccb52ab9 Date: Tue, 27 Apr 2021 09:20:23 +0000 (GMT) [thread overview] Message-ID: <20210427092023.C26633835828@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 ae50e86ee44eac14e1fcf291f799c3c8ccb52ab9 (commit) from 4f1583a7659e8800f1e240e8b90cc4bcd26f0130 (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 ae50e86ee44eac14e1fcf291f799c3c8ccb52ab9 Author: Richard Biener <rguenther@suse.de> Date: Tue Apr 27 11:19:31 2021 +0200 Document BB vectorizer improvements diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html index 5090ec43..a74e188e 100644 --- a/htdocs/gcc-11/changes.html +++ b/htdocs/gcc-11/changes.html @@ -167,6 +167,15 @@ You may also want to check out our use <code>-g</code> together with <code>-gdwarf-2</code>, <code>-gdwarf-3</code> or <code>-gdwarf-4</code>. </li> + <li> + Vectorizer improvements: + <ul> + <li>The straight-line code vectorizer now considers the whole function + when vectorizing and can handle opportunities crossing CFG merges + and backedges. + </li> + </ul> + </li> <li> Inter-procedural optimization improvements: <ul> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/changes.html | 9 +++++++++ 1 file changed, 9 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-04-27 9:20 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=20210427092023.C26633835828@sourceware.org \ --to=rguenth@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).