On 12/06/17 23:28 +0100, Pedro Alves wrote:
On 06/05/2017 03:27 PM, Jonathan Wakely wrote:
Pedro, this is OK for trunk now we're in stage 1. Please go ahead and
commit it - thanks.
Thanks Jonathan. I've pushed it in now.
It's probably safe for gcc-7-branch too, but let's leave it on trunk
On 06/05/2017 03:27 PM, Jonathan Wakely wrote:
> Pedro, this is OK for trunk now we're in stage 1. Please go ahead and
> commit it - thanks.
Thanks Jonathan. I've pushed it in now.
>
> It's probably safe for gcc-7-branch too, but let's leave it on trunk
> for a while first.
OK.
BTW, for extr
On 23/04/17 19:33 +0100, Pedro Alves wrote:
On 04/23/2017 06:54 PM, Pedro Alves wrote:
Hi!
As I had suggested in PR c++/80265, here's a patch that uses
__builtin_constant_p to tell whether we can defer to a constexpr
algorithm, which avoids having to wait for compiler support.
Unfortunately I
9b9a3ea79bd790d792c9a02e5a577f1af156 Mon Sep 17 00:00:00 2001
From: Pedro Alves
Date: Sun, 23 Apr 2017 14:16:09 +0100
Subject: [PATCH] Finish implementing P0426R1 "Constexpr for std::char_traits"
for C++17
As discussed in PR c++/80265 (__builtin_{memcmp,memchr,strlen} are not
usable in c
Sun, 23 Apr 2017 14:16:09 +0100
Subject: [PATCH] Finish implementing P0426R1 "Constexpr for std::char_traits"
for C++17
As discussed in PR c++/80265 (__builtin_{memcmp,memchr,strlen} are not
usable in constexpr functions), use __builtin_constant_p to tell
whether we can defer to a const
