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/89229] Incorrect xmm16-xmm31/ymm16-ymm31 in vector move Date: Mon, 16 Mar 2020 10:52:53 +0000 [thread overview] Message-ID: <bug-89229-4-zPovt5JZdi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-89229-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 --- Comment #34 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:5a3c42b227bbe9e7acb5335088d2255262311bd8 commit r10-7189-g5a3c42b227bbe9e7acb5335088d2255262311bd8 Author: H.J. Lu <hjl.tools@gmail.com> Date: Mon Mar 16 03:48:55 2020 -0700 i386: Use ix86_output_ssemov for SImode TYPE_SSEMOV There is no need to set mode attribute to XImode since ix86_output_ssemov can properly encode xmm16-xmm31 registers with and without AVX512VL. Remove ext_sse_reg_operand since it is no longer needed. gcc/ PR target/89229 * config/i386/i386.md (*movsi_internal): Call ix86_output_ssemov for TYPE_SSEMOV. Remove ext_sse_reg_operand and TARGET_AVX512VL check. * config/i386/predicates.md (ext_sse_reg_operand): Removed. gcc/testsuite/ PR target/89229 * gcc.target/i386/pr89229-7a.c: New test. * gcc.target/i386/pr89229-7b.c: Likewise. * gcc.target/i386/pr89229-7c.c: Likewise.
next prev parent reply other threads:[~2020-03-16 10:52 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-89229-4@http.gcc.gnu.org/bugzilla/> 2020-03-11 12:07 ` marxin at gcc dot gnu.org 2020-03-12 12:38 ` marxin at gcc dot gnu.org 2020-03-13 10:28 ` marxin at gcc dot gnu.org 2020-03-14 23:12 ` cvs-commit at gcc dot gnu.org 2020-03-15 17:23 ` cvs-commit at gcc dot gnu.org 2020-03-16 10:52 ` cvs-commit at gcc dot gnu.org [this message] 2020-03-16 10:54 ` hjl.tools at gmail dot com
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-89229-4-zPovt5JZdi@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).