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-8234] Daily bump. Date: Sun, 24 Apr 2022 00:17:15 +0000 (GMT) [thread overview] Message-ID: <20220424001715.F271D3858C2C@sourceware.org> (raw) https://gcc.gnu.org/g:afe0b5b7ce597641f02d47f0384610fb078a2cb7 commit r12-8234-gafe0b5b7ce597641f02d47f0384610fb078a2cb7 Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Sun Apr 24 00:16:27 2022 +0000 Daily bump. Diff: --- gcc/ChangeLog | 7 +++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 5 +++++ 3 files changed, 13 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index d2470b938b8..a3bcf1dd1fb 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,10 @@ +2022-04-23 Jakub Jelinek <jakub@redhat.com> + + PR target/105338 + * config/i386/i386-expand.cc (ix86_expand_int_movcc): Handle + op0 == cst1 ? op0 : op3 like op0 == cst1 ? cst1 : op3 for the non-cmov + cases. + 2022-04-22 Segher Boessenkool <segher@kernel.crashing.org> PR target/105334 diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index 9759b529eb5..76bd88aee70 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20220423 +20220424 diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index b5eef7be347..cad4990f5c3 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2022-04-23 Jakub Jelinek <jakub@redhat.com> + + PR target/105338 + * gcc.target/i386/pr105338.c: New test. + 2022-04-22 Mikael Morin <mikael@gcc.gnu.org> Richard Biener <rguenther@suse.de>
reply other threads:[~2022-04-24 0:17 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=20220424001715.F271D3858C2C@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).