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/98694] GCC produces incorrect code for loops with -O3 for skylake-avx512 and icelake-server Date: Tue, 10 May 2022 08:17:58 +0000 [thread overview] Message-ID: <bug-98694-4-7GTJeLlsHo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98694-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98694 --- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:0372a414e7500dccab1eb423a2a620645c820a52 commit r10-10611-g0372a414e7500dccab1eb423a2a620645c820a52 Author: liuhongt <hongtao.liu@intel.com> Date: Mon Jan 18 16:55:32 2021 +0800 Fix incorrect optimization by cprop_hardreg. If SRC had been assigned a mode narrower than the copy, we can't always link DEST into the chain even they have same hard_regno_nregs(i.e. HImode/SImode in i386 backend). i.e kmovw %k0, %edi vmovd %edi, %xmm2 vpshuflw $0, %xmm2, %xmm0 kmovw %k0, %r8d kmovd %k0, %r9d ... - movl %r9d, %r11d + vmovd %xmm2, %r11d gcc/ChangeLog: PR rtl-optimization/98694 * regcprop.c (copy_value): If SRC had been assigned a mode narrower than the copy, we can't link DEST into the chain even they have same hard_regno_nregs(i.e. HImode/SImode in i386 backend). gcc/testsuite/ChangeLog: PR rtl-optimization/98694 * gcc.target/i386/pr98694.c: New test. (cherry picked from commit e711b67a9081ae84c66174a50705dc98ba993a43)
next prev parent reply other threads:[~2022-05-10 8:17 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-15 1:42 [Bug tree-optimization/98694] New: " vsevolod.livinskij at frtk dot ru 2021-01-15 8:11 ` [Bug tree-optimization/98694] " crazylht at gmail dot com 2021-01-15 9:43 ` [Bug target/98694] " marxin at gcc dot gnu.org 2021-01-15 10:03 ` [Bug target/98694] [11 Regression] " rguenth at gcc dot gnu.org 2021-01-15 16:52 ` crazylht at gmail dot com 2021-01-15 16:56 ` crazylht at gmail dot com 2021-01-15 17:22 ` crazylht at gmail dot com 2021-01-15 17:33 ` crazylht at gmail dot com 2021-01-18 9:41 ` crazylht at gmail dot com 2021-01-21 5:30 ` cvs-commit at gcc dot gnu.org 2021-01-21 5:33 ` crazylht at gmail dot com 2021-01-21 9:41 ` [Bug target/98694] " rguenth at gcc dot gnu.org 2021-01-21 11:12 ` crazylht at gmail dot com 2021-05-05 17:48 ` jakub at gcc dot gnu.org 2022-05-10 8:17 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-28 23:30 ` pinskia 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-98694-4-7GTJeLlsHo@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).