From: Jonathan Wakely <jwakely@redhat.com>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH 2/2] libstdc++: mark 20_util/scoped_allocator/noexcept.cc R-E-T hosted
Date: Thu, 9 Nov 2023 19:34:34 +0000 [thread overview]
Message-ID: <CACb0b4=HhAGy5i_vHov7fmPc28Ox=eTWX81y9EJ-KxU1eLmAFA@mail.gmail.com> (raw)
In-Reply-To: <20231109193009.2391070-2-arsen@aarsen.me>
On Thu, 9 Nov 2023 at 19:32, Arsen Arsenović <arsen@aarsen.me> wrote:
>
> libstdc++-v3/ChangeLog:
>
> * testsuite/20_util/scoped_allocator/noexcept.cc: Mark as
> requiring hosted.
OK for trunk, thanks.
The test has been backported, but we don't have the hosted et there so
this isn't needed on the branches.
> ---
> libstdc++-v3/testsuite/20_util/scoped_allocator/noexcept.cc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/libstdc++-v3/testsuite/20_util/scoped_allocator/noexcept.cc b/libstdc++-v3/testsuite/20_util/scoped_allocator/noexcept.cc
> index 16992968d3b9..f14eff2c46f5 100644
> --- a/libstdc++-v3/testsuite/20_util/scoped_allocator/noexcept.cc
> +++ b/libstdc++-v3/testsuite/20_util/scoped_allocator/noexcept.cc
> @@ -1,4 +1,5 @@
> // { dg-do compile { target c++11 } }
> +// { dg-require-effective-target hosted }
>
> #include <scoped_allocator>
>
> --
> 2.42.1
>
next prev parent reply other threads:[~2023-11-09 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 19:25 [PATCH 1/2] libstdc++: declare std::allocator in !HOSTED as an extension Arsen Arsenović
2023-11-09 19:25 ` [PATCH 2/2] libstdc++: mark 20_util/scoped_allocator/noexcept.cc R-E-T hosted Arsen Arsenović
2023-11-09 19:34 ` Jonathan Wakely [this message]
2023-11-09 23:07 ` [PATCH 1/2] libstdc++: declare std::allocator in !HOSTED as an extension Jonathan Wakely
2023-11-09 23:09 ` Arsen Arsenović
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='CACb0b4=HhAGy5i_vHov7fmPc28Ox=eTWX81y9EJ-KxU1eLmAFA@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=arsen@aarsen.me \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
/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).