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-8561] Daily bump. Date: Sun, 10 Jul 2022 00:19:41 +0000 (GMT) [thread overview] Message-ID: <20220710001941.6BBF638582A7@sourceware.org> (raw) https://gcc.gnu.org/g:7282722666c2bc43a4f10dcb88b100f8fe4d7bcc commit r12-8561-g7282722666c2bc43a4f10dcb88b100f8fe4d7bcc Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Sun Jul 10 00:19:06 2022 +0000 Daily bump. Diff: --- gcc/ChangeLog | 8 ++++++++ gcc/DATESTAMP | 2 +- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index e34775c433f..38d4c7983bd 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,11 @@ +2022-07-09 Roger Sayle <roger@nextmovesoftware.com> + Uroš Bizjak <ubizjak@gmail.com> + + PR target/105930 + * config/i386/i386.md (*<any_or>di3_doubleword): Split after + reload. Use rtx_equal_p to avoid creating memory-to-memory moves, + and emit NOTE_INSN_DELETED if operand[2] is zero (i.e. with -O0). + 2022-07-08 Lulu Cheng <chenglulu@loongson.cn> Backported from master: diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 2f349b0ec04..6de1e01bae4 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20220709 +20220710
reply other threads:[~2022-07-10 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=20220710001941.6BBF638582A7@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).