From: Jonathan Wakely <jwakely@redhat.com>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 2/2] libstdc++: Fix a few !HOSTED test regressions
Date: Fri, 13 Jan 2023 14:17:29 +0000 [thread overview]
Message-ID: <CACb0b4=5PdjsttEtkRFuDVE1OaHXJOZ0qGrkqbfp4TwBfKteUQ@mail.gmail.com> (raw)
In-Reply-To: <20230110100305.1420589-2-arsen@aarsen.me>
On Tue, 10 Jan 2023 at 10:03, Arsen Arsenović via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> libstdc++-v3/ChangeLog:
>
> * testsuite/20_util/to_chars/version.cc: Mark hosted-only.
> * testsuite/20_util/uses_allocator/lwg3677.cc: Ditto.
> * testsuite/20_util/weak_ptr/cons/self_move.cc: Ditto.
> * testsuite/std/ranges/adaptors/as_rvalue/1.cc: Replace usage of
> std::make_unique with a freestanding-compatible wrapper around
> unique_ptr.
> * testsuite/21_strings/basic_string_view/operations/contains/char.cc:
> Don't test for presence of __cpp_lib_string_contains on !HOSTED.
> * testsuite/21_strings/basic_string_view/operations/contains/char/2.cc:
> Ditto.
> * testsuite/std/ranges/version_c++23.cc: Don't test for presence
> of __cpp_lib_ranges in !HOSTED.
Tested powerpc64le-linux and pushed to trunk, thanks!
next prev parent reply other threads:[~2023-01-13 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 10:03 [PATCH 1/2] libstdc++: Enable string_view in freestanding Arsen Arsenović
2023-01-10 10:03 ` [PATCH 2/2] libstdc++: Fix a few !HOSTED test regressions Arsen Arsenović
2023-01-13 14:17 ` Jonathan Wakely [this message]
2023-01-10 14:26 ` [PATCH 1/2] libstdc++: Enable string_view in freestanding Jonathan Wakely
2023-01-10 16:19 ` Arsen Arsenović
2023-01-13 14:17 ` 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='CACb0b4=5PdjsttEtkRFuDVE1OaHXJOZ0qGrkqbfp4TwBfKteUQ@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).