From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 111180 invoked by alias); 19 Jun 2019 19:12:08 -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 111162 invoked by uid 89); 19 Jun 2019 19:12:07 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE,KAM_SHORT autolearn=ham version=3.3.1 spammy=H*i:CAH6eHdS9j71zb, H*f:CAH6eHdS9j71zb, H*i:mnU, H*i:sk:E-50uH6 X-HELO: mx.coeval.ca Received: from mx.coeval.ca (HELO mx.coeval.ca) (184.75.211.21) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 19 Jun 2019 19:12:06 +0000 Received: from mail-oi1-f178.google.com (mail-oi1-f178.google.com [209.85.167.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx.coeval.ca (Postfix) with ESMTPSA id 0007B436054 for ; Wed, 19 Jun 2019 19:12:04 +0000 (UTC) Received: by mail-oi1-f178.google.com with SMTP id w79so165575oif.10 for ; Wed, 19 Jun 2019 12:12:04 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Reply-To: joel@rtems.org From: Joel Sherrill Date: Wed, 19 Jun 2019 19:12:00 -0000 Message-ID: Subject: Re: C++17 Support and Website To: Jonathan Wakely Cc: GCC Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-06/txt/msg00199.txt.bz2 On Wed, Jun 19, 2019 at 2:07 PM Jonathan Wakely wrote: > On Wed, 19 Jun 2019 at 20:05, Joel Sherrill wrote: > > > > Hi > > > > I was double checking the C++17 support in GCC for someone and the text > at > > this URL states > > the support is experimental and gives the impression that the support is > > incomplete. The table > > of language features now has them all implemented. > > > > Is this text still accurate? > > No, see the 9.1.0 announcement: > https://gcc.gnu.org/ml/gcc-announce/2019/msg00001.html > > > https://gcc.gnu.org/projects/cxx-status.html#cxx17 > > We should fix that, thanks! > Thanks for the quick reply. If it is any consolation, LLVM's status page appears to similarly suffer from not getting the introductory text updated.