public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108724] [11 Regression] Poor codegen when summing two arrays without AVX or SSE Date: Tue, 23 May 2023 12:55:13 +0000 [thread overview] Message-ID: <bug-108724-4-0TyGQneCxj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108724-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108724 --- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> --- On trunk we're back to vectorizing but as intended with DImode which makes us save half of the loads and stores and we think the extended required arithmetic covers up for that (by quite some margin). movabsq $9223372034707292159, %rcx movq (%rdx), %rax movq (%rsi), %rsi movq %rcx, %rdx andq %rax, %rdx andq %rsi, %rcx xorq %rsi, %rax addq %rcx, %rdx movabsq $-9223372034707292160, %rcx andq %rcx, %rax xorq %rdx, %rax movq %rax, (%rdi) vs movl (%rdx), %eax addl (%rsi), %eax movl %eax, (%rdi) movl 4(%rdx), %eax addl 4(%rsi), %eax movl %eax, 4(%rdi)
next prev parent reply other threads:[~2023-05-23 12:55 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-08 19:17 [Bug target/108724] New: [11 regression] " gbs at canishe dot com 2023-02-08 19:30 ` [Bug tree-optimization/108724] " pinskia at gcc dot gnu.org 2023-02-09 9:37 ` crazylht at gmail dot com 2023-02-09 13:54 ` rguenth at gcc dot gnu.org 2023-02-10 10:00 ` rguenth at gcc dot gnu.org 2023-02-10 10:07 ` [Bug tree-optimization/108724] [11/12/13 Regression] " rguenth at gcc dot gnu.org 2023-02-10 11:22 ` cvs-commit at gcc dot gnu.org 2023-02-10 11:22 ` [Bug tree-optimization/108724] [11/12 " rguenth at gcc dot gnu.org 2023-03-15 9:48 ` cvs-commit at gcc dot gnu.org 2023-05-05 8:34 ` [Bug tree-optimization/108724] [11 " rguenth at gcc dot gnu.org 2023-05-05 12:06 ` [Bug target/108724] " rguenth at gcc dot gnu.org 2023-05-23 12:55 ` rguenth at gcc dot gnu.org [this message] 2023-05-29 10:08 ` jakub 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-108724-4-0TyGQneCxj@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).