From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "Kay F. Jahnke" <kfjahnke@gmail.com>
Cc: Andrew Haley <aph@redhat.com>,
Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: autovectorization in gcc
Date: Thu, 10 Jan 2019 11:18:00 -0000 [thread overview]
Message-ID: <CAH6eHdTSS44gXoj37ST36e_8Yp2smtDOrLYeDzqo2ss8vSkSWw@mail.gmail.com> (raw)
In-Reply-To: <fe90e977-540e-1e30-1e36-16de143904a2@gmail.com>
On Thu, 10 Jan 2019 at 09:25, Kay F. Jahnke wrote:
> Documentation is absolutely essential. If there is lots of development
> in autovectorization, not documenting this work in a way users can
> simply find is - in my eyes - a grave omission. The text
> 'Auto-vectorization in GCC' looks like it has last been updated in 2011
> (according to the 'Latest News' section). I'm curious to know what new
> capabilities have been added since then.
The page you're looking at documents the project to *add*
autovectorization to GCC. That project was completed many years ago,
and the feature has been present in GCC for years.
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.
next prev parent reply other threads:[~2019-01-10 11:18 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 [this message]
2019-08-18 10:59 ` [wwwdocs PATCH] for " Gerald Pfeifer
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=CAH6eHdTSS44gXoj37ST36e_8Yp2smtDOrLYeDzqo2ss8vSkSWw@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--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).