From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12438 invoked by alias); 10 Jan 2019 11:18:57 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 12423 invoked by uid 89); 10 Jan 2019 11:18:57 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=grave, interest, documents X-HELO: mail-wr1-f50.google.com Received: from mail-wr1-f50.google.com (HELO mail-wr1-f50.google.com) (209.85.221.50) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 10 Jan 2019 11:18:55 +0000 Received: by mail-wr1-f50.google.com with SMTP id z5so10882006wrt.11 for ; Thu, 10 Jan 2019 03:18:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZYybLziJOG0IqhHmXdhar51Sja5IXgixqrz1QMnj2gs=; b=YQq3A/qvKf+J0WjgYTWl0K71DR639UpS8XKqt9fTnuEgUtUsS6O7jJrpIHJFryUqJv ImtXP6ZYne6SVH58nQ5+Ax57rQiPmG1FvAX/+3mrgNr8Ia5fJ87KOvSVKE55h9x9EAwO 2Svc3hQxQYDEHYFW01cez1RtU+OfeyGqgQ6APbJzq9wODcD3D1WTZQoDyAQ2mU31APd7 0Pw50yZcmmgq5vvDOwNUQiZAEjDdvp6xKP4M6ANddJxEB7xX99NlM5RBPfOHcZYPxjYI s0Y9y18M9YP55AINXL5bsCWDeDZ/EnEll9HgfBlQ824uYqXj8GauJ0QkRYRSfGyjxls3 KvtQ== MIME-Version: 1.0 References: <41ea83cd-0ce8-4f25-35e5-888513d69c7b@gmail.com> <5C35C2C2.1050106@foss.arm.com> <2721bb39-ee4b-0202-d81d-e0b36d2059fa@redhat.com> In-Reply-To: From: Jonathan Wakely Date: Thu, 10 Jan 2019 11:18:00 -0000 Message-ID: Subject: Re: autovectorization in gcc To: "Kay F. Jahnke" Cc: Andrew Haley , Kyrill Tkachov , "gcc@gcc.gnu.org" Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-01/txt/msg00068.txt.bz2 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.