From: Gerald Pfeifer <gerald@pfeifer.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: "Kay F. Jahnke" <kfjahnke@gmail.com>,
Andrew Haley <aph@redhat.com>,
Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [wwwdocs PATCH] for Re: autovectorization in gcc
Date: Sun, 18 Aug 2019 10:59:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.21.1908181256130.14047@anthias.pfeifer.com> (raw)
In-Reply-To: <CAH6eHdTSS44gXoj37ST36e_8Yp2smtDOrLYeDzqo2ss8vSkSWw@mail.gmail.com>
On Thu, 10 Jan 2019, Jonathan Wakely wrote:
>> [ https://gcc.gnu.org/projects/tree-ssa/vectorization.html ]
> I'm not disputing that there could be better documentation, but that
> page is not the place to find it. That page should probably get a
> notice added saying that the project is complete and that the page is
> now only of historical interest.
Like this? ;-)
Committed.
Gerald
Index: projects/tree-ssa/vectorization.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/tree-ssa/vectorization.html,v
retrieving revision 1.42
diff -u -r1.42 vectorization.html
--- projects/tree-ssa/vectorization.html 30 Sep 2018 14:38:57 -0000 1.42
+++ projects/tree-ssa/vectorization.html 18 Aug 2019 10:55:46 -0000
@@ -2,15 +2,17 @@
<html lang="en">
<head>
- <title>Auto-vectorization in GCC</title>
+<title>Auto-vectorization in GCC</title>
<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css" />
</head>
<body>
<h1>Auto-vectorization in GCC<br /></h1>
- <p>The goal of this project is to develop a loop and basic block vectorizer in
- GCC, based on the <a href="./">tree-ssa</a> framework.</p>
+ <p>The goal of this project was to develop a loop and basic block
+ vectorizer in GCC, based on the <a href="./">tree-ssa</a> framework.
+ It has been completed and the functionality has been part of GCC
+ for years.</p>
<h2>Table of Contents</h2>
next prev parent reply other threads:[~2019-08-18 10:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 8:29 Kay F. Jahnke
2019-01-09 9:46 ` Kyrill Tkachov
2019-01-09 9:50 ` Andrew Haley
2019-01-09 9:56 ` Jonathan Wakely
2019-01-09 16:10 ` David Malcolm
2019-01-09 16:25 ` Jakub Jelinek
2019-01-10 8:19 ` Richard Biener
2019-01-10 11:11 ` Szabolcs Nagy
2019-01-09 16:26 ` David Malcolm
2019-01-09 10:47 ` Ramana Radhakrishnan
2019-01-10 9:24 ` Kay F. Jahnke
2019-01-10 11:18 ` Jonathan Wakely
2019-08-18 10:59 ` Gerald Pfeifer [this message]
2019-01-09 10:56 ` Kay F. Jahnke
2019-01-09 11:03 ` Jakub Jelinek
2019-01-09 11:21 ` Jakub Jelinek
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.LSU.2.21.1908181256130.14047@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=kfjahnke@gmail.com \
--cc=kyrylo.tkachov@foss.arm.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).