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-9931] Daily bump. Date: Fri, 20 Oct 2023 00:19:35 +0000 (GMT) [thread overview] Message-ID: <20231020001935.66EF23858D1E@sourceware.org> (raw) https://gcc.gnu.org/g:7d99d9a6d2c739407c1ce56599cf6cfb61c4aa0c commit r12-9931-g7d99d9a6d2c739407c1ce56599cf6cfb61c4aa0c Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Fri Oct 20 00:19:10 2023 +0000 Daily bump. Diff: --- gcc/ChangeLog | 9 +++++++++ gcc/DATESTAMP | 2 +- 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 300d836f2c7b..b702f8e32045 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,12 @@ +2023-10-19 Richard Sandiford <richard.sandiford@arm.com> + + Backported from master: + 2023-09-07 Richard Sandiford <richard.sandiford@arm.com> + + PR target/111528 + * lra-eliminations.cc (lra_eliminate_regs_1): Use simplify_gen_binary + rather than gen_rtx_PLUS. + 2023-10-16 Kewen Lin <linkw@linux.ibm.com> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 1e71ea70cb34..5402eeba5fc7 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20231019 +20231020
reply other threads:[~2023-10-20 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=20231020001935.66EF23858D1E@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).