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: Gerald Pfeifer <gerald@pfeifer.com>,
	Jason Merrill <jason@redhat.com>,
	       gcc-patches@gcc.gnu.org
Subject: Re: [C++ PATCH] Implement LWG2296 helper intrinsic
Date: Tue, 03 Jan 2017 10:55:00 -0000	[thread overview]
Message-ID: <20170103105509.GC895@redhat.com> (raw)
In-Reply-To: <20170101145323.GX21933@tucnak>

[-- Attachment #1: Type: text/plain, Size: 629 bytes --]

On 01/01/17 15:53 +0100, Jakub Jelinek wrote:
>On Sun, Jan 01, 2017 at 10:27:24AM -0400, Gerald Pfeifer wrote:
>> On Fri, 7 Oct 2016, Jakub Jelinek wrote:
>> > The following patch adds __builtin_addressof with the semantics it has in
>> > clang, i.e. it is a constexpr & operator alternative that never uses the
>> > overloaded & operator.
>>
>> Nice!
>>
>> Are you planning to document this in gcc-7/changes.html ?
>
>We shouldn't document the builtin, but that std::addressof is usable in
>constexpr contexts.  I'll defer documentation thereof to Jon, together with
>other libstdc++ changes.

I've committed this to wwwdocs.



[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 1686 bytes --]

? htdocs/gcc-7/.changes.html.swp
Index: htdocs/gcc-7/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-7/changes.html,v
retrieving revision 1.32
diff -u -r1.32 changes.html
--- htdocs/gcc-7/changes.html	27 Nov 2016 12:54:13 -0000	1.32
+++ htdocs/gcc-7/changes.html	3 Jan 2017 10:54:01 -0000
@@ -287,13 +287,30 @@
       <code>std::chrono::round</code>, and <code>std::chrono::abs</code>;
     </li>
     <li>
-      <code>std::clamp</code>;
+      <code>std::clamp</code>, <code>std::gcd</code>, <code>std::lcm</code>,
+      3-dimensional <code>std::hypot</code>;
+    </li>
+    <li><code>std::shared_mutex</code>;</li>
+    <li><code>std::default_searcher</code>,
+      <code>std::boyer_moore_searcher</code> and
+      <code>std::boyer_moore_horspool_searcher</code>;
+    </li>
+    <li>
+      Extraction and re-insertion of map and set nodes, <code>try_emplace</code>
+      members for maps, and functions for accessing containers
+      <code>std::size</code>, <code>std::empty</code>, and
+      <code>std::data</code>;
     </li>
     <li>
+      <code>std::shared_ptr</code> support for arrays,
       <code>std::shared_ptr&lt;T&gt;::weak_type</code>,
       <code>std::enable_shared_from_this&lt;T&gt;::weak_from_this()</code>,
       and <code>std::owner_less&lt;void&gt;</code>;
     </li>
+    <li><code>std::as_const</code>, <code>std::not_fn</code>,
+      <code>std::has_unique_object_representations</code>,
+      constexpr <code>std::addressof</code>.
+    </li>
   </ul>
   Thanks to Daniel Kr&uuml;gler, Tim Shen, Edward Smith-Rowland, and Ville Voutilainen for
   work on the C++17 support.

      reply	other threads:[~2017-01-03 10:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 19:23 Jakub Jelinek
2016-10-07 19:34 ` Jason Merrill
2017-01-01 14:27 ` Gerald Pfeifer
2017-01-01 14:53   ` Jakub Jelinek
2017-01-03 10:55     ` Jonathan Wakely [this message]

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=20170103105509.GC895@redhat.com \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --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).