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-11112] Daily bump.
Date: Sat, 25 Nov 2023 00:19:38 +0000 (GMT)	[thread overview]
Message-ID: <20231125001939.006153858CD1@sourceware.org> (raw)

https://gcc.gnu.org/g:9cb5130716289efd1ee4687c87969c59f4e8119f

commit r11-11112-g9cb5130716289efd1ee4687c87969c59f4e8119f
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Sat Nov 25 00:19:15 2023 +0000

    Daily bump.

Diff:
---
 gcc/ChangeLog           | 9 +++++++++
 gcc/DATESTAMP           | 2 +-
 gcc/testsuite/ChangeLog | 8 ++++++++
 3 files changed, 18 insertions(+), 1 deletion(-)

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index ffb8fd49912..833b2bfc155 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,12 @@
+2023-11-24  Uros Bizjak  <ubizjak@gmail.com>
+
+	Backported from master:
+	2023-11-23  Uros Bizjak  <ubizjak@gmail.com>
+
+	PR target/112672
+	* config/i386/i386.md (parityhi2):
+	Use temporary register in the call to gen_parityhi2_cmp.
+
 2023-11-22  Maciej W. Rozycki  <macro@embecosm.com>
 
 	Backported from master:
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 0222a31d594..07c89b4503c 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20231124
+20231125
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 8731d2b8d6e..e1e5b2e1d3f 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,11 @@
+2023-11-24  Uros Bizjak  <ubizjak@gmail.com>
+
+	Backported from master:
+	2023-11-23  Uros Bizjak  <ubizjak@gmail.com>
+
+	PR target/112672
+	* gcc.target/i386/pr112672.c: New test.
+
 2023-11-22  Maciej W. Rozycki  <macro@embecosm.com>
 
 	Backported from master:

                 reply	other threads:[~2023-11-25  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=20231125001939.006153858CD1@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).