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/95046] Vectorize V2SFmode operations Date: Fri, 15 May 2020 07:25:23 +0000 [thread overview] Message-ID: <bug-95046-4-bnGcE9pFNV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95046-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95046 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Uros Bizjak <uros@gcc.gnu.org>: https://gcc.gnu.org/g:f4356120ba88c083dd5987376aab7590dd1e0e13 commit r11-409-gf4356120ba88c083dd5987376aab7590dd1e0e13 Author: Uros Bizjak <ubizjak@gmail.com> Date: Fri May 15 09:24:38 2020 +0200 i386: Add V2SFmode hadd/hsub instructions [PR95046] PFACC/PFNACC 3dNow! instructions got their corresponding SSE alternative in SSE3, so these can't be implemented with TARGET_MMX_WITH_SSE, which implies SSE2. These instructions are only generated via builtins, and since several 3dNow! insns have no corresponding SSE alternative, we can't avoid MMX registers with 3dNow! builtins anyway. Add SSE3/AVX alternatives to the insn pattern, so compiler will be able to use XMM registers when available, but don't prevent MMX registers, since they are needed when SSE3 is not active. Add additional generic insn patterns, used by the combiner to synthesize horizontal V2SFmode add/sub instructions. These patterns are active for TARGET_MMX_WITH_SSE only, and use only XMM registers. gcc/ChangeLog: PR target/95046 * config/i386/i386.md (isa): Add sse3_noavx. (enabled): Handle sse3_noavx. * config/i386/mmx.md (mmx_haddv2sf3): New expander. (*mmx_haddv2sf3): Rename from mmx_haddv2sf3. Add SSE/AVX alternatives. Match commutative vec_select selector operands. (*mmx_haddv2sf3_low): New insn pattern. (*mmx_hsubv2sf3): Add SSE/AVX alternatives. (*mmx_hsubv2sf3_low): New insn pattern. testsuite/ChangeLog: PR target/95046 * gcc.target/i386/pr95046-8.c: New test.
next prev parent reply other threads:[~2020-05-15 7:25 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-11 7:12 [Bug target/95046] New: " ubizjak at gmail dot com 2020-05-11 7:13 ` [Bug target/95046] " ubizjak at gmail dot com 2020-05-11 7:13 ` ubizjak at gmail dot com 2020-05-11 9:17 ` cvs-commit at gcc dot gnu.org 2020-05-11 14:39 ` cvs-commit at gcc dot gnu.org 2020-05-11 18:13 ` cvs-commit at gcc dot gnu.org 2020-05-12 15:06 ` cvs-commit at gcc dot gnu.org 2020-05-12 15:08 ` cvs-commit at gcc dot gnu.org 2020-05-12 16:38 ` cvs-commit at gcc dot gnu.org 2020-05-12 17:25 ` cvs-commit at gcc dot gnu.org 2020-05-14 7:16 ` cvs-commit at gcc dot gnu.org 2020-05-14 11:48 ` cvs-commit at gcc dot gnu.org 2020-05-14 17:52 ` cvs-commit at gcc dot gnu.org 2020-05-15 7:25 ` cvs-commit at gcc dot gnu.org [this message] 2020-05-15 8:03 ` cvs-commit at gcc dot gnu.org 2020-12-10 9:45 ` ubizjak at gmail dot com 2021-06-29 17:18 ` cvs-commit at gcc dot gnu.org 2021-12-24 16:10 ` cvs-commit at gcc dot gnu.org 2021-12-27 9:12 ` cvs-commit 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-95046-4-bnGcE9pFNV@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).