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-10327] Daily bump. Date: Fri, 21 Oct 2022 00:20:48 +0000 (GMT) [thread overview] Message-ID: <20221021002048.0314D3858D37@sourceware.org> (raw) https://gcc.gnu.org/g:2229c1fcfa205d6f4907d397fe7366aa76b1da07 commit r11-10327-g2229c1fcfa205d6f4907d397fe7366aa76b1da07 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Fri Oct 21 00:20:10 2022 +0000 Daily bump. Diff: --- gcc/ChangeLog | 30 ++++++++++++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 22 ++++++++++++++++++++++ 3 files changed, 53 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 3bd1f9c8f2a..a036ead0833 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,33 @@ +2022-10-20 Richard Sandiford <richard.sandiford@arm.com> + + Backported from master: + 2022-10-20 Richard Sandiford <richard.sandiford@arm.com> + + * config/aarch64/aarch64-sve.md (*aarch64_brk<brk_op>_cc): Remove + merging alternative. + (*aarch64_brk<brk_op>_ptest): Likewise. + +2022-10-20 Richard Sandiford <richard.sandiford@arm.com> + + Backported from master: + 2022-10-20 Richard Sandiford <richard.sandiford@arm.com> + + * config/aarch64/iterators.md (SVE_BRKP): New iterator. + * config/aarch64/aarch64-sve.md (*aarch64_brkn_cc): New pattern. + (*aarch64_brkn_ptest): Likewise. + (*aarch64_brk<brk_op>_cc): Restrict to SVE_BRKP. + (*aarch64_brk<brk_op>_ptest): Likewise. + +2022-10-20 Richard Sandiford <richard.sandiford@arm.com> + + * config/aarch64/aarch64.h (AARCH64_FL_FOR_ARCH8_3): Add + AARCH64_FL_RCPC. + (AARCH64_ISA_RCPC): New macro. + * config/aarch64/aarch64-cores.def (thunderx3t110, zeus, neoverse-v1) + (neoverse-512tvb, saphira): Remove RCPC from these Armv8.3-A+ cores. + * config/aarch64/aarch64-c.c (aarch64_update_cpp_builtins): Define + __ARM_FEATURE_RCPC when appropriate. + 2022-10-19 Kewen Lin <linkw@linux.ibm.com> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 8b08eddd863..0f7d77c700e 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20221020 +20221021 diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index a38e9279450..9bc97c1d891 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,25 @@ +2022-10-20 Richard Sandiford <richard.sandiford@arm.com> + + Backported from master: + 2022-10-20 Richard Sandiford <richard.sandiford@arm.com> + + * gcc.target/aarch64/sve/acle/general/brka_1.c: Expect a separate + PTEST instruction. + * gcc.target/aarch64/sve/acle/general/brkb_1.c: Likewise. + +2022-10-20 Richard Sandiford <richard.sandiford@arm.com> + + Backported from master: + 2022-10-20 Richard Sandiford <richard.sandiford@arm.com> + + * gcc.target/aarch64/sve/acle/general/brkn_1.c: Expect separate + PTEST instructions. + * gcc.target/aarch64/sve/acle/general/brkn_2.c: New test. + +2022-10-20 Richard Sandiford <richard.sandiford@arm.com> + + * gcc.target/aarch64/pragma_cpp_predefs_1.c: Add RCPC tests. + 2022-10-19 Kewen Lin <linkw@linux.ibm.com> Backported from master:
reply other threads:[~2022-10-21 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=20221021002048.0314D3858D37@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).