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 r12-5561] Daily bump.
Date: Sun, 28 Nov 2021 00:16:54 +0000 (GMT)	[thread overview]
Message-ID: <20211128001654.1C18D385840F@sourceware.org> (raw)

https://gcc.gnu.org/g:d62c8c747ca4be9cfb78218d5daf4158bffe4c2b

commit r12-5561-gd62c8c747ca4be9cfb78218d5daf4158bffe4c2b
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Sun Nov 28 00:16:20 2021 +0000

    Daily bump.

Diff:
---
 gcc/ChangeLog           | 21 +++++++++++++++++++++
 gcc/DATESTAMP           |  2 +-
 gcc/jit/ChangeLog       |  4 ++++
 gcc/testsuite/ChangeLog | 10 ++++++++++
 libgcc/ChangeLog        |  4 ++++
 5 files changed, 40 insertions(+), 1 deletion(-)

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index e1e381e1905..232da26bc57 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,24 @@
+2021-11-27  Jakub Jelinek  <jakub@redhat.com>
+
+	PR middle-end/103431
+	* config/i386/i386.md (x86_64_shld, x86_shld, x86_64_shrd, x86_shrd):
+	Change insn pattern to accurately describe the instructions.
+	(*x86_64_shld_1, *x86_shld_1, *x86_64_shrd_1, *x86_shrd_1): New
+	define_insn patterns.
+	(*x86_64_shld_2, *x86_shld_2, *x86_64_shrd_2, *x86_shrd_2): New
+	define_insn_and_split patterns.
+	(*ashl<dwi>3_doubleword_mask, *ashl<dwi>3_doubleword_mask_1,
+	*<insn><dwi>3_doubleword_mask, *<insn><dwi>3_doubleword_mask_1,
+	ix86_rotl<dwi>3_doubleword, ix86_rotr<dwi>3_doubleword): Adjust
+	splitters for x86_{,64_}sh{l,r}d pattern changes.
+
+2021-11-27  Jakub Jelinek  <jakub@redhat.com>
+
+	PR tree-optimization/103435
+	* gimple-ssa-store-merging.c (find_bswap_or_nop_finalize): Avoid UB if
+	n->range - rsize == 8, just clear both *cmpnop and *cmpxchg in that
+	case.
+
 2021-11-27  Martin Jambor  <mjambor@suse.cz>
 
 	PR ipa/103441
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 22f794c7a9c..4fdb99fbfe2 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20211127
+20211128
diff --git a/gcc/jit/ChangeLog b/gcc/jit/ChangeLog
index f5a836ac62c..2a36b533cbc 100644
--- a/gcc/jit/ChangeLog
+++ b/gcc/jit/ChangeLog
@@ -1,3 +1,7 @@
+2021-11-27  Petter Tomner  <tomner@kth.se>
+
+	* libgccjit.c: %ld -> %zu
+
 2021-11-24  Martin Liska  <mliska@suse.cz>
 
 	* jit-playback.c (function): Initialize m_blocks vector.
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 182c649b67e..11ffdcf269e 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,13 @@
+2021-11-27  Jakub Jelinek  <jakub@redhat.com>
+
+	PR middle-end/103431
+	* gcc.dg/pr103431.c: New test.
+
+2021-11-27  Roger Sayle  <roger@nextmovesoftware.com>
+
+	* gcc.dg/tree-ssa/ivopts-8.c: Fix new test case for -m32.
+	* gcc.dg/tree-ssa/ivopts-9.c: Likewise.
+
 2021-11-26  Harald Anlauf  <anlauf@gmx.de>
 
 	PR fortran/103411
diff --git a/libgcc/ChangeLog b/libgcc/ChangeLog
index bf3cad2d3aa..3f01b7000ea 100644
--- a/libgcc/ChangeLog
+++ b/libgcc/ChangeLog
@@ -1,3 +1,7 @@
+2021-11-27  John David Anglin  <danglin@gcc.gnu.org>
+
+	* config/pa/t-dimode (lib2difuncs): Fix typo.
+
 2021-11-25  Florian Weimer  <fweimer@redhat.com>
 
 	* unwind-dw2-fde-dip.c (struct unw_eh_callback_data): Add hdr.


                 reply	other threads:[~2021-11-28  0:16 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=20211128001654.1C18D385840F@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).