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-8414] Daily bump.
Date: Wed, 25 May 2022 00:19:57 +0000 (GMT) [thread overview]
Message-ID: <20220525001957.D5D94383B789@sourceware.org> (raw)
https://gcc.gnu.org/g:ed843f13146a0c753f33299ec37605cc5ec463d8
commit r12-8414-ged843f13146a0c753f33299ec37605cc5ec463d8
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date: Wed May 25 00:19:20 2022 +0000
Daily bump.
Diff:
---
gcc/ChangeLog | 29 +++++++++++++++++++++++++++++
gcc/DATESTAMP | 2 +-
gcc/testsuite/ChangeLog | 37 +++++++++++++++++++++++++++++++++++++
3 files changed, 67 insertions(+), 1 deletion(-)
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 6fb72a0d33f..eab10802422 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,32 @@
+2022-05-24 Qing Zhao <qing.zhao@oracle.com>
+
+ Backported from master:
+ 2022-05-09 Qing Zhao <qing.zhao@oracle.com>
+
+ PR target/101891
+ * config/i386/i386.cc (zero_call_used_regno_mode): use V2SImode
+ as a generic MMX mode instead of V4HImode.
+ (zero_all_mm_registers): Use SET to zero instead of MOV for
+ zeroing scratch registers.
+ (ix86_zero_call_used_regs): Likewise.
+
+2022-05-24 Bruno Haible <bruno@clisp.org>
+
+ Backported from master:
+ 2022-05-24 Bruno Haible <bruno@clisp.org>
+
+ PR other/105527
+ * doc/install.texi (Configuration): Add more details about --with-zstd.
+ Document --with-zstd-include and --with-zstd-lib
+
+2022-05-24 Martin Liska <mliska@suse.cz>
+
+ Backported from master:
+ 2022-05-11 Martin Liska <mliska@suse.cz>
+
+ PR other/105527
+ * doc/install.texi: Document the configure option --with-zstd.
+
2022-05-20 Peter Bergner <bergner@linux.ibm.com>
Backported from master:
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 7d93d3872a3..a0acbbdde33 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20220524
+20220525
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 61a03e70174..484b727dda0 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,40 @@
+2022-05-24 Qing Zhao <qing.zhao@oracle.com>
+
+ Backported from master:
+ 2022-05-09 Qing Zhao <qing.zhao@oracle.com>
+
+ * gcc.target/i386/zero-scratch-regs-1.c: Add -fno-stack-protector
+ -fno-PIC.
+ * gcc.target/i386/zero-scratch-regs-10.c: Adjust mov to xor.
+ * gcc.target/i386/zero-scratch-regs-13.c: Add -msse.
+ * gcc.target/i386/zero-scratch-regs-14.c: Adjust mov to xor.
+ * gcc.target/i386/zero-scratch-regs-15.c: Add -fno-stack-protector
+ -fno-PIC.
+ * gcc.target/i386/zero-scratch-regs-16.c: Likewise.
+ * gcc.target/i386/zero-scratch-regs-17.c: Likewise.
+ * gcc.target/i386/zero-scratch-regs-18.c: Add -fno-stack-protector
+ -fno-PIC, adjust mov to xor.
+ * gcc.target/i386/zero-scratch-regs-19.c: Add -fno-stack-protector
+ -fno-PIC.
+ * gcc.target/i386/zero-scratch-regs-2.c: Adjust mov to xor.
+ * gcc.target/i386/zero-scratch-regs-20.c: Add -msse.
+ * gcc.target/i386/zero-scratch-regs-21.c: Add -fno-stack-protector
+ -fno-PIC, Adjust mov to xor.
+ * gcc.target/i386/zero-scratch-regs-22.c: Adjust mov to xor.
+ * gcc.target/i386/zero-scratch-regs-23.c: Likewise.
+ * gcc.target/i386/zero-scratch-regs-26.c: Likewise.
+ * gcc.target/i386/zero-scratch-regs-27.c: Likewise.
+ * gcc.target/i386/zero-scratch-regs-28.c: Likewise.
+ * gcc.target/i386/zero-scratch-regs-3.c: Add -fno-stack-protector.
+ * gcc.target/i386/zero-scratch-regs-31.c: Adjust mov to xor.
+ * gcc.target/i386/zero-scratch-regs-4.c: Add -fno-stack-protector
+ -fno-PIC.
+ * gcc.target/i386/zero-scratch-regs-5.c: Adjust mov to xor.
+ * gcc.target/i386/zero-scratch-regs-6.c: Add -fno-stack-protector.
+ * gcc.target/i386/zero-scratch-regs-7.c: Likewise.
+ * gcc.target/i386/zero-scratch-regs-8.c: Adjust mov to xor.
+ * gcc.target/i386/zero-scratch-regs-9.c: Add -fno-stack-protector.
+
2022-05-20 Richard Biener <rguenther@suse.de>
Backported from master:
reply other threads:[~2022-05-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=20220525001957.D5D94383B789@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).