public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: GCC Administrator <gccadmin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r10-10445] Daily bump.
Date: Thu, 10 Feb 2022 00:18:11 +0000 (GMT) [thread overview]
Message-ID: <20220210001811.DF6773858D1E@sourceware.org> (raw)
https://gcc.gnu.org/g:a7b8564a8932e55c7a7ac02a879afd24745d5ba5
commit r10-10445-ga7b8564a8932e55c7a7ac02a879afd24745d5ba5
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date: Thu Feb 10 00:17:35 2022 +0000
Daily bump.
Diff:
---
gcc/ChangeLog | 12 ++++++++++++
gcc/DATESTAMP | 2 +-
gcc/testsuite/ChangeLog | 10 ++++++++++
3 files changed, 23 insertions(+), 1 deletion(-)
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 033abfab8a5..378e2ac3339 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,15 @@
+2022-02-09 Uroš Bizjak <ubizjak@gmail.com>
+
+ PR target/104458
+ * config/i386/i386-expand.c (ix86_split_idivmod):
+ Force operands[2] and operands[3] into a register..
+
+2022-02-09 liuhongt <hongtao.liu@intel.com>
+
+ PR target/104451
+ * config/i386/sse.md (<insn><mode>3): lowpart_subreg
+ operands[2] from SImode to QImode.
+
2022-02-03 Sebastian Huber <sebastian.huber@embedded-brains.de>
PR target/104090
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index eef289ae020..65c020f9c5e 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20220209
+20220210
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 85f4fe48b44..24bbecfabc8 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,13 @@
+2022-02-09 Uroš Bizjak <ubizjak@gmail.com>
+
+ PR target/104458
+ * gcc.target/i386/pr104458.c: New test.
+
+2022-02-09 liuhongt <hongtao.liu@intel.com>
+
+ PR target/104451
+ * gcc.target/i386/pr104451.c: New test.
+
2022-02-04 Harald Anlauf <anlauf@gmx.de>
Backported from master:
reply other threads:[~2022-02-10 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=20220210001811.DF6773858D1E@sourceware.org \
--to=gccadmin@gcc.gnu.org \
--cc=gcc-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).