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/116274] [14/15 Regression] x86: poor code generation with 16 byte function arguments and addition Date: Thu, 15 Aug 2024 11:15:35 +0000 [thread overview] Message-ID: <bug-116274-4-QMlUwwgQ1a@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-116274-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116274 --- Comment #7 from GCC 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:f7e672da8fc3d416a6d07eb01f3be4400ef94fac commit r15-2930-gf7e672da8fc3d416a6d07eb01f3be4400ef94fac Author: liuhongt <hongtao.liu@intel.com> Date: Mon Aug 12 18:24:34 2024 +0800 Movement between GENERAL_REGS and SSE_REGS for TImode doesn't need secondary reload. It results in 2 failures for x86_64-pc-linux-gnu{\ -march=cascadelake}; gcc: gcc.target/i386/extendditi3-1.c scan-assembler cqt?o gcc: gcc.target/i386/pr113560.c scan-assembler-times \tmulq 1 For pr113560.c, now GCC generates mulx instead of mulq with -march=cascadelake, which should be optimal, so adjust testcase for that. For gcc.target/i386/extendditi2-1.c, RA happens to choose another register instead of rax and result in movq %rdi, %rbp movq %rdi, %rax sarq $63, %rbp movq %rbp, %rdx The patch adds a new define_peephole2 for that. gcc/ChangeLog: PR target/116274 * config/i386/i386-expand.cc (ix86_expand_vector_move): Restrict special case TImode to 128-bit vector conversions via V2DI under ix86_pre_reload_split (). * config/i386/i386.cc (inline_secondary_memory_needed): Movement between GENERAL_REGS and SSE_REGS for TImode doesn't need secondary reload. * config/i386/i386.md (*extendsidi2_rex64): Add a define_peephole2 after it. gcc/testsuite/ChangeLog: * gcc.target/i386/pr116274.c: New test. * gcc.target/i386/pr113560.c: Scan either mulq or mulx.
next prev parent reply other threads:[~2024-08-15 11:15 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-08-07 18:08 [Bug c/116274] New: x86: poor code generation with 16 byte function arguments ripatel at wii dot dev 2024-08-07 18:11 ` [Bug target/116274] [14/15 Regression] " pinskia at gcc dot gnu.org 2024-08-08 9:07 ` [Bug target/116274] [14/15 Regression] x86: poor code generation with 16 byte function arguments and addition rguenth at gcc dot gnu.org 2024-08-08 9:52 ` rguenth at gcc dot gnu.org 2024-08-12 8:19 ` liuhongt at gcc dot gnu.org 2024-08-12 9:41 ` liuhongt at gcc dot gnu.org 2024-08-12 10:18 ` liuhongt at gcc dot gnu.org 2024-08-15 11:15 ` cvs-commit at gcc dot gnu.org [this message] 2024-08-15 11:16 ` liuhongt at gcc dot gnu.org 2024-08-20 7:53 ` rguenth at gcc dot gnu.org 2024-08-20 11:02 ` cvs-commit at gcc dot gnu.org 2024-09-18 9:30 ` [Bug target/116274] [14 " cvs-commit at gcc dot gnu.org 2024-09-18 9:34 ` rguenth 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-116274-4-QMlUwwgQ1a@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).