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 r12-8481] Daily bump.
Date: Wed, 15 Jun 2022 00:19:49 +0000 (GMT) [thread overview]
Message-ID: <20220615001949.83C46385829E@sourceware.org> (raw)
https://gcc.gnu.org/g:e11091012fed75eb1148699a7a5662e5f72a57f0
commit r12-8481-ge11091012fed75eb1148699a7a5662e5f72a57f0
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date: Wed Jun 15 00:19:12 2022 +0000
Daily bump.
Diff:
---
gcc/ChangeLog | 20 ++++++++++++++++++++
gcc/DATESTAMP | 2 +-
libstdc++-v3/ChangeLog | 18 ++++++++++++++++++
3 files changed, 39 insertions(+), 1 deletion(-)
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index afdc7be58a1..6eb98d22050 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,23 @@
+2022-06-14 H.J. Lu <hjl.tools@gmail.com>
+
+ Backported from master:
+ 2022-06-13 H.J. Lu <hjl.tools@gmail.com>
+
+ * common/config/i386/cpuinfo.h (get_available_features): Require
+ AVX for F16C and VAES.
+
+2022-06-14 Philipp Tomsich <philipp.tomsich@vrull.eu>
+
+ Backported from master:
+ 2022-06-02 Philipp Tomsich <philipp.tomsich@vrull.eu>
+
+ * config/riscv/riscv.cc (riscv_build_integer_1): Rewrite value as
+ (-1 << 31) for the single-bit case, when operating on (1 << 31)
+ in SImode.
+ * config/riscv/riscv.h (SINGLE_BIT_MASK_OPERAND): Allow for
+ any single-bit value, moving the special case for (1 << 31) to
+ riscv_build_integer_1 (in riscv.c).
+
2022-06-08 Max Filippov <jcmvbkbc@gmail.com>
Backported from master:
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index f6e8eb7c21b..fa673f38835 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20220614
+20220615
diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index 35a74b52730..d7fe5f7ea34 100644
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -1,3 +1,21 @@
+2022-06-14 Jonathan Wakely <jwakely@redhat.com>
+
+ Backported from master:
+ 2022-06-13 Jonathan Wakely <jwakely@redhat.com>
+
+ * include/std/atomic (__atomic_val_t): Use __type_identity_t
+ instead of atomic<T>::value_type, as per LWG 3220.
+ * testsuite/29_atomics/atomic/lwg3220.cc: New test.
+
+2022-06-14 Mark Mentovai <mark@mentovai.com>
+
+ Backported from master:
+ 2022-06-13 Mark Mentovai <mark@mentovai.com>
+
+ * include/experimental/bits/fs_path.h (__detail::__null_terminated):
+ Rename to __nul_terminated to avoid colliding with a macro in
+ Apple's SDK.
+
2022-06-08 Jonathan Wakely <jwakely@redhat.com>
Backported from master:
reply other threads:[~2022-06-15 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=20220615001949.83C46385829E@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: 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).