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-10511] Daily bump.
Date: Wed, 8 Feb 2023 00:19:59 +0000 (GMT) [thread overview]
Message-ID: <20230208002000.420F53858D33@sourceware.org> (raw)
https://gcc.gnu.org/g:f18f568caf24417a11396065a654c9b9b79264b3
commit r11-10511-gf18f568caf24417a11396065a654c9b9b79264b3
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date: Wed Feb 8 00:19:20 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 71e2e4b509e..35cf9f4db44 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,12 @@
+2023-02-07 Richard Biener <rguenther@suse.de>
+
+ Backported from master:
+ 2022-09-02 Richard Biener <rguenther@suse.de>
+
+ PR tree-optimization/106809
+ * tree-ssa-sccvn.c (dominaged_by_p_w_unex): Check we have
+ more than one successor before doing extra work.
+
2023-02-02 Martin Jambor <mjambor@suse.cz>
Backported from master:
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 9e62c1c1935..a48b5a401cf 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20230207
+20230208
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 05679b89434..268db69334e 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,11 @@
+2023-02-07 Richard Biener <rguenther@suse.de>
+
+ Backported from master:
+ 2022-09-02 Richard Biener <rguenther@suse.de>
+
+ PR tree-optimization/106809
+ * gcc.dg/torture/pr106809.c: New testcase.
+
2023-02-04 Harald Anlauf <anlauf@gmx.de>
Backported from master:
reply other threads:[~2023-02-08 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=20230208002000.420F53858D33@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).