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-10400] Daily bump. Date: Wed, 30 Nov 2022 00:21:11 +0000 (GMT) [thread overview] Message-ID: <20221130002111.4E6B73858D1E@sourceware.org> (raw) https://gcc.gnu.org/g:885f5c3d5763d46e02bd2f192765cb589b4c4fe4 commit r11-10400-g885f5c3d5763d46e02bd2f192765cb589b4c4fe4 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Wed Nov 30 00:20:30 2022 +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 80d9e220900..5093ea0f1ce 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,12 @@ +2022-11-29 Max Filippov <jcmvbkbc@gmail.com> + + Backported from master: + 2022-11-08 Max Filippov <jcmvbkbc@gmail.com> + + PR rtl-optimization/107482 + * ira-color.c (assign_hard_reg): Only call + update_costs_from_copies when retry_p is false. + 2022-11-25 Eric Botcazou <ebotcazou@adacore.com> * range-op.cc (operator_bitwise_xor::op1_range): Fix thinko. diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 7063790611d..e6a7597e85b 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20221129 +20221130
reply other threads:[~2022-11-30 0:21 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=20221130002111.4E6B73858D1E@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).