public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/89984] Extra register move Date: Mon, 06 Sep 2021 12:18:25 +0000 [thread overview] Message-ID: <bug-89984-4-TpQvsXRcVp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-89984-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89984 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by H.J. Lu <hjl@gcc.gnu.org>: https://gcc.gnu.org/g:652bef70d392f9541b12ef65b461009c8c8fd54a commit r12-3369-g652bef70d392f9541b12ef65b461009c8c8fd54a Author: H.J. Lu <hjl.tools@gmail.com> Date: Sat Sep 4 08:28:00 2021 -0700 x86: Add non-destructive source to @xorsign<mode>3_1 Add non-destructive source alternative to @xorsign<mode>3_1 for AVX. gcc/ PR target/89984 * config/i386/i386-expand.c (ix86_split_xorsign): Use operands[2]. * config/i386/i386.md (@xorsign<mode>3_1): Add non-destructive source alternative for AVX. gcc/testsuite/ PR target/89984 * gcc.target/i386/pr89984-1.c: New test. * gcc.target/i386/pr89984-2.c: Likewise. * gcc.target/i386/xorsign-avx.c: Likewise.
next prev parent reply other threads:[~2021-09-06 12:18 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-89984-4@http.gcc.gnu.org/bugzilla/> 2021-09-01 8:42 ` pinskia at gcc dot gnu.org 2021-09-04 6:41 ` pinskia at gcc dot gnu.org 2021-09-06 12:18 ` cvs-commit at gcc dot gnu.org [this message] 2021-09-06 12:35 ` hjl.tools at gmail dot com 2021-09-08 8:24 ` jakub at gcc dot gnu.org 2021-09-08 12:09 ` cvs-commit at gcc dot gnu.org 2021-09-08 12:11 ` jakub at gcc dot gnu.org
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=bug-89984-4-TpQvsXRcVp@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).