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/105504] Fails to break dependency for vcvtss2sd xmm, xmm, mem Date: Wed, 08 Jun 2022 03:24:53 +0000 [thread overview] Message-ID: <bug-105504-4-si4BZvePF3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105504-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105504 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>: https://gcc.gnu.org/g:5e005393d4ff0a428c5f55b9ba7f65d6078a7cf5 commit r13-1009-g5e005393d4ff0a428c5f55b9ba7f65d6078a7cf5 Author: liuhongt <hongtao.liu@intel.com> Date: Mon May 30 15:30:51 2022 +0800 Disparages SSE_REGS alternatives sligntly with ?v instead of *v in *mov{si,di}_internal. So alternative v won't be igored in record_reg_classess. Similar for *r alternatives in some vector patterns. It helps testcase in the PR, also RA now makes better decisions for gcc.target/i386/extract-insert-combining.c movd %esi, %xmm0 movd %edi, %xmm1 - movl %esi, -12(%rsp) paddd %xmm0, %xmm1 pinsrd $0, %esi, %xmm0 paddd %xmm1, %xmm0 The patch has no big impact on SPEC2017 for both O2 and Ofast march=native run. And I noticed there's some changes in SPEC2017 from code like mov mem, %eax vmovd %eax, %xmm0 .. mov %eax, 64(%rsp) to vmovd mem, %xmm0 .. vmovd %xmm0, 64(%rsp) Which should be exactly what we want? gcc/ChangeLog: PR target/105513 PR target/105504 * config/i386/i386.md (*movsi_internal): Change alternative from *v to ?v. (*movdi_internal): Ditto. * config/i386/sse.md (vec_set<mode>_0): Change alternative *r to ?r. (*vec_extractv4sf_mem): Ditto. (*vec_extracthf): Ditto. gcc/testsuite/ChangeLog: * gcc.target/i386/pr105513-1.c: New test. * gcc.target/i386/extract-insert-combining.c: Add new scan-assembler-not for spill.
next prev parent reply other threads:[~2022-06-08 3:24 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-06 9:12 [Bug target/105504] New: " amonakov at gcc dot gnu.org 2022-05-07 3:02 ` [Bug target/105504] " crazylht at gmail dot com 2022-05-07 3:16 ` crazylht at gmail dot com 2022-05-07 3:36 ` crazylht at gmail dot com 2022-05-07 4:04 ` crazylht at gmail dot com 2022-05-07 8:28 ` amonakov at gcc dot gnu.org 2022-06-08 3:24 ` cvs-commit at gcc dot gnu.org [this message] 2023-08-05 15:05 ` egallager at gcc dot gnu.org 2023-08-07 1:55 ` crazylht at gmail dot com 2023-08-12 13:50 ` egallager 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-105504-4-si4BZvePF3@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).