public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: GCC Administrator <gccadmin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r13-5703] Daily bump. Date: Sun, 5 Feb 2023 00:18:04 +0000 (GMT) [thread overview] Message-ID: <20230205001804.AF20F3858C31@sourceware.org> (raw) https://gcc.gnu.org/g:057eb31bc322b080dab87a52ad5629e3a439df82 commit r13-5703-g057eb31bc322b080dab87a52ad5629e3a439df82 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Sun Feb 5 00:16:45 2023 +0000 Daily bump. Diff: --- gcc/DATESTAMP | 2 +- libstdc++-v3/ChangeLog | 18 ++++++++++++++++++ 2 files changed, 19 insertions(+), 1 deletion(-) diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 65026ee2abb..40ef8d39af3 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20230204 +20230205 diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 77e54a8573e..f64f761f409 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,21 @@ +2023-02-04 Hans-Peter Nilsson <hp@axis.com> + + PR libstdc++/108672 + * include/pstl/unseq_backend_simd.h (__simd_or): Use __INT32_TYPE__ + instead of int32_t. + +2023-02-04 Gerald Pfeifer <gerald@pfeifer.com> + + * doc/xml/manual/documentation_hacking.xml: Adjust link to pdftex. + * doc/html/manual/documentation_hacking.html: Regenerate. + +2023-02-04 François Dumont <fdumont@gcc.gnu.org> + + * include/bits/basic_string.h (operator=(basic_string&&)): Transfer move-to + storage to the move-from instance when allocators are equal. + * testsuite/21_strings/basic_string/allocator/char/move_assign.cc (test04): + New test case. + 2023-02-03 Samuel Thibault <samuel.thibault@gnu.org> * config/os/gnu-linux/os_defines.h [!__linux__]
reply other threads:[~2023-02-05 0:18 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230205001804.AF20F3858C31@sourceware.org \ --to=gccadmin@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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: linkBe 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).