From: Szabolcs Nagy <Szabolcs.Nagy@arm.com>
To: Jonathan Wakely <jwakely@redhat.com>,
"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: nd <nd@arm.com>
Subject: Re: [PATCH] Add noexcept to tuple<> and simplify tuple<T1,T2> noexcept-specifiers
Date: Mon, 03 Jun 2019 09:44:00 -0000 [thread overview]
Message-ID: <6a07e458-c242-c95c-5716-6d1b442e1553@arm.com> (raw)
In-Reply-To: <20190531145802.GA602@redhat.com>
On 31/05/2019 15:58, Jonathan Wakely wrote:
> * include/std/tuple (tuple<>): Add noexcept to allocator-extended
> constructors.
> (tuple<T1, T2>::__nothrow_default_constructible()): New helper
> function.
> (tuple<T1, T2>::tuple(), explicit tuple<T1, T2>::tuple()): Use helper.
>
> Tested powerpc64le-linux, committed to trunk.
on aarch64* i see
FAIL: g++.dg/cpp0x/noexcept15.C -std=c++14 (test for excess errors)
In file included from /S/gcc/testsuite/g++.dg/cpp0x/noexcept15.C:4:
/B/aarch64-none-linux-gnu/libstdc++-v3/include/type_traits: In instantiation of 'struct std::is_nothrow_move_constructible<Blob>':
/S/gcc/testsuite/g++.dg/cpp0x/noexcept15.C:14:5: required from 'single<Tp>::single(single<Tp>&&) [with Tp = Blob]'
/S/gcc/testsuite/g++.dg/cpp0x/noexcept15.C:23:51: required from 'constexpr single<typename std::decay<_Tp>::type> make_single(Tp&&) [with Tp =
Blob&; typename std::decay<_Tp>::type = Blob]'
/S/gcc/testsuite/g++.dg/cpp0x/noexcept15.C:31:18: required from here
/B/aarch64-none-linux-gnu/libstdc++-v3/include/type_traits:1111:52: error: static assertion failed: template argument must be a complete class
or an unbounded array
next prev parent reply other threads:[~2019-06-03 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 15:19 Jonathan Wakely
2019-06-03 9:44 ` Szabolcs Nagy [this message]
2019-06-03 9:46 ` 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=6a07e458-c242-c95c-5716-6d1b442e1553@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=nd@arm.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).