public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jason Merrill <jason@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: Patch ping (Re: [wwwdocs] Add __cpp_* feature macros to C++20 entries + other changes that have those in projects/cxx_status.html)
Date: Mon, 21 Jan 2019 16:11:00 -0000	[thread overview]
Message-ID: <20190121161104.GZ15627@redhat.com> (raw)
In-Reply-To: <20190121134053.GJ30353@tucnak>

On 21/01/19 14:40 +0100, Jakub Jelinek wrote:
>Hi!
>
>On Sat, Jan 12, 2019 at 02:08:15PM +0100, Jakub Jelinek wrote:
>> Here is an updated patch, that in addition to that makes 9 URLs as we now
>> have #cxx in gcc-9/changes.html and adds missing P0941R2 entry that clang
>> table has.  For that one I'm not 100% sure what to say, I've copied all the
>> macros from http://wg21.link/p0941r2 into two source files (attached below),
>> one for core language features, another one for library and tested those
>> with -std=c++2a with current trunk.  Compared to what the paper lists, we
>> have __has_cpp_attribute (carries_dependency) 0, __cpp_guaranteed_copy_elision
>> and __cpp_nontype_template_parameter_auto not defined.  Is that what we
>> want?  On the library side, __cpp_lib_any, __cpp_lib_execution,
>> __cpp_lib_hardware_interference_size, __cpp_lib_null_iterators,
>> __cpp_lib_parallel_algorithm, __cpp_lib_raw_memory_algorithms,
>> __cpp_lib_to_chars, __cpp_lib_uncaught_exceptions, __cpp_lib_variant
>> macros aren't defined (at least not in <version>) and
>> __cpp_lib_optional, __cpp_lib_shared_ptr_arrays, __cpp_lib_string_view
>> have smaller values than those in the P0941R2.
>> Is that the desirable state given current C++2A implementation status?
>>
>> Ok for wwwdocs (or do you suggest something different for the P0941R2
>> imlementation status)?
>
>I'd like to ping this patch.

For P0941R2 I think we can just say it's supported. For the library
docs I said we support it since GCC 5.1 because that's when we started
defining feature test macros. The point of the paper is to define
macros for the features that are supported, and we've been doing that
for years. If a macro is missing, it's because we don't support the
feature yet, and that's a correct implementation of the macro!

  reply	other threads:[~2019-01-21 16:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 15:54 [wwwdocs] Add __cpp_* feature macros to C++20 entries that have those in projects/cxx_status.html Jakub Jelinek
2019-01-12 13:08 ` [wwwdocs] Add __cpp_* feature macros to C++20 entries + other changes " Jakub Jelinek
2019-01-12 15:04   ` Gerald Pfeifer
2019-01-12 17:30     ` Jakub Jelinek
2019-01-15 11:10   ` Jonathan Wakely
2019-01-21 13:41   ` Patch ping (Re: [wwwdocs] Add __cpp_* feature macros to C++20 entries + other changes that have those in projects/cxx_status.html) Jakub Jelinek
2019-01-21 16:11     ` Jonathan Wakely [this message]
2019-01-21 16:36       ` Jakub Jelinek
2019-01-21 17:19         ` Jonathan Wakely

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=20190121161104.GZ15627@redhat.com \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jason@redhat.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).