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 r14-6875] Daily bump. Date: Mon, 1 Jan 2024 00:19:42 +0000 (GMT) [thread overview] Message-ID: <20240101001942.A64D63858C20@sourceware.org> (raw) https://gcc.gnu.org/g:3a7dd24eadeb918f9990db7adcb3e63e76bd63fb commit r14-6875-g3a7dd24eadeb918f9990db7adcb3e63e76bd63fb Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Mon Jan 1 00:18:40 2024 +0000 Daily bump. Diff: --- gcc/ChangeLog | 7 +++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 6 ++++++ libstdc++-v3/ChangeLog | 25 +++++++++++++++++++++++++ 4 files changed, 39 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 63f746b2c25..c55e0f46c17 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,10 @@ +2023-12-31 Uros Bizjak <ubizjak@gmail.com> + Roger Sayle <roger@nextmovesoftware.com> + + PR target/43644 + * config/i386/i386.md (*add<dwi>3_doubleword_concat_zext): Tweak + order of instructions after split, to minimize number of moves. + 2023-12-29 Jan Hubicka <jh@suse.cz> * config/i386/x86-tune.def (X86_TUNE_AVOID_128FMA_CHAINS, diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index d3a1eb5640c..72e8e2938b8 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20231231 +20240101 diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index 6b2f90853af..7e37126ebee 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,9 @@ +2023-12-31 Uros Bizjak <ubizjak@gmail.com> + Roger Sayle <roger@nextmovesoftware.com> + + PR target/43644 + * gcc.target/i386/pr43644-2.c: Expect 2 movq instructions. + 2023-12-30 Martin Uecker <uecker@tugraz.at> * gcc.dg/c23-tag-9.c: New test. diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 2e0407adfc6..f97165b4992 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,28 @@ +2023-12-31 Hans-Peter Nilsson <hp@axis.com> + + * testsuite/20_util/hash/quality.cc: Increase timeout by a factor 3. + +2023-12-31 François Dumont <fdumont@gcc.gnu.org> + + * include/bits/hashtable.h: Move comment about all equivalent values + being next to each other in the class documentation header. + (_M_reinsert_node, _M_merge_unique): Implement small size optimization. + (_M_find_tr, _M_count_tr, _M_equal_range_tr): Likewise. + +2023-12-31 François Dumont <fdumont@gcc.gnu.org> + + * testsuite/performance/23_containers/insert/54075.cc: Add lookup on unknown entries + w/o copy to see potential impact of memory fragmentation enhancements. + * testsuite/performance/23_containers/insert/unordered_multiset_hint.cc: Enhance hash + functor to make it perfect, exactly 1 entry per bucket. Also use hash functor tagged as + slow or not to bench w/o hash code cache. + * testsuite/performance/23_containers/insert/unordered_set_hint.cc: New test case. Like + previous one but using std::unordered_set. + * testsuite/performance/23_containers/insert/unordered_set_range_insert.cc: New test case. + Check performance of range-insertion compared to individual insertions. + * testsuite/performance/23_containers/insert_erase/unordered_small_size.cc: Add same bench + but after a copy to demonstrate impact of enhancements regarding memory fragmentation. + 2023-12-22 Christophe Lyon <christophe.lyon@linaro.org> * Makefile.am: Allow overriding EXEPCT.
reply other threads:[~2024-01-01 0:19 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=20240101001942.A64D63858C20@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).