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-10418] Daily bump.
Date: Tue, 13 Dec 2022 00:21:09 +0000 (GMT)	[thread overview]
Message-ID: <20221213002109.95002385516C@sourceware.org> (raw)

https://gcc.gnu.org/g:870027ed71e9fed249c50405c9bc0562ced3cbfe

commit r11-10418-g870027ed71e9fed249c50405c9bc0562ced3cbfe
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Tue Dec 13 00:20:28 2022 +0000

    Daily bump.

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

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 91baa4b78c5..cf1de8ba9be 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,13 @@
+2022-12-12  Richard Biener  <rguenther@suse.de>
+
+	Backported from master:
+	2022-10-06  Richard Biener  <rguenther@suse.de>
+
+	PR tree-optimization/107107
+	* tree-ssa-sccvn.c (visit_reference_op_store): Do not
+	affect value-numbering when doing the tail merging
+	MODIFY_EXPR lookup.
+
 2022-12-01  liuhongt  <hongtao.liu@intel.com>
 
 	PR target/107863
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index a8efd513898..349ad3e1070 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20221212
+20221213
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 31b2c1f9681..b32d4b85576 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,11 @@
+2022-12-12  Richard Biener  <rguenther@suse.de>
+
+	Backported from master:
+	2022-10-06  Richard Biener  <rguenther@suse.de>
+
+	PR tree-optimization/107107
+	* gcc.dg/pr107107.c: New testcase.
+
 2022-12-11  Iain Buclaw  <ibuclaw@gdcproject.org>
 
 	Backported from master:

                 reply	other threads:[~2022-12-13  0:21 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=20221213002109.95002385516C@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).