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 r11-11066] Daily bump.
Date: Wed, 18 Oct 2023 00:19:34 +0000 (GMT) [thread overview]
Message-ID: <20231018001934.677173858CDB@sourceware.org> (raw)
https://gcc.gnu.org/g:546e574d88ccd4abcaf59d7c26559b11611f33cb
commit r11-11066-g546e574d88ccd4abcaf59d7c26559b11611f33cb
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date: Wed Oct 18 00:19:10 2023 +0000
Daily bump.
Diff:
---
gcc/ChangeLog | 10 ++++++++++
gcc/DATESTAMP | 2 +-
gcc/testsuite/ChangeLog | 7 +++++++
3 files changed, 18 insertions(+), 1 deletion(-)
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index ef7e57e8e5e9..7c3f8b7c4ded 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,13 @@
+2023-10-17 liuhongt <hongtao.liu@intel.com>
+
+ Backported from master:
+ 2023-07-06 liuhongt <hongtao.liu@intel.com>
+
+ PR target/110170
+ * config/i386/i386.md (movdf_internal): Disparage slightly for
+ 2 alternatives (r,v) and (v,r) by adding constraint modifier
+ '?'.
+
2023-10-07 Andrew Pinski <pinskia@gmail.com>
Backported from master:
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index a8fe11db53a8..304d62621454 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20231017
+20231018
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index a5e9fa44b40f..5c5373b342c1 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,10 @@
+2023-10-17 liuhongt <hongtao.liu@intel.com>
+
+ Backported from master:
+ 2023-07-06 liuhongt <hongtao.liu@intel.com>
+
+ * gcc.target/i386/pr110170-3.c: New test.
+
2023-10-07 Andrew Pinski <pinskia@gmail.com>
Backported from master:
reply other threads:[~2023-10-18 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=20231018001934.677173858CDB@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).