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-8570] Daily bump. Date: Fri, 15 Jul 2022 00:20:01 +0000 (GMT) [thread overview] Message-ID: <20220715002001.95EF13858C55@sourceware.org> (raw) https://gcc.gnu.org/g:b8102d1ea4bfdf38cb8c4bd2cebdc9cafbcdf0ff commit r12-8570-gb8102d1ea4bfdf38cb8c4bd2cebdc9cafbcdf0ff Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Fri Jul 15 00:19:21 2022 +0000 Daily bump. Diff: --- gcc/ChangeLog | 14 ++++++++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 8 ++++++++ 3 files changed, 23 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index e80d4016f99..aee305e16a7 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,17 @@ +2022-07-14 Michael Meissner <meissner@linux.ibm.com> + + * config/rs6000/rs6000.cc (rs6000_option_override_internal): Do + not generate block copies with vector pair instructions if we are + tuning for power10. Back port from master branch. + +2022-07-14 Surya Kumari Jangala <jskumari@linux.vnet.ibm.com> + + Backported from master: + 2022-06-14 Surya Kumari Jangala <jskumari@linux.ibm.com> + + PR rtl-optimization/105041 + * regrename.cc (check_new_reg_p): Use nregs value from du chain. + 2022-07-11 Martin Jambor <mjambor@suse.cz> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 56754ca716d..5d08726610c 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20220714 +20220715 diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index 64076cb7864..84899b9873e 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,11 @@ +2022-07-14 Surya Kumari Jangala <jskumari@linux.vnet.ibm.com> + + Backported from master: + 2022-06-14 Surya Kumari Jangala <jskumari@linux.ibm.com> + + PR rtl-optimization/105041 + * gcc.target/powerpc/pr105041.c: New test. + 2022-07-11 Martin Jambor <mjambor@suse.cz> Backported from master:
reply other threads:[~2022-07-15 0:20 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=20220715002001.95EF13858C55@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: linkBe 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).