public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "d_vampile at 163 dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110026] New: [Bug] 5% performance drop on important benchmark after r260951. Date: Mon, 29 May 2023 15:14:27 +0000 [thread overview] Message-ID: <bug-110026-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110026 Bug ID: 110026 Summary: [Bug] 5% performance drop on important benchmark after r260951. Product: gcc Version: 10.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: d_vampile at 163 dot com Target Milestone: --- Created attachment 55184 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55184&action=edit Open-source stream benchmark After the patch is submitted on AArch64, the performance of copying subitems in the stream benchmark decreases by 3%. Alternatively, you can obtain it from https://github.com/jeffhammond/stream/archive/master.zip. Compiling & Running: gcc -fopenmp -O -DSTREAM_ARRAY_SIZE=100000000 stream.c -o stream ./stream Before modification: (copy subitem) ldr x2, [x3, x0, lsl #3] str x2, [x4, x0, lsl #3] add x0, x0, #0x1 cmp x1, x0 b.ne 400a00 <main._omp_fn.4+0x54> ldr x19, [sp, #16] ldp x29, x30, [sp], #32 ret After the modification: ldr d0, [x2, x0, lsl #3] str d0, [x3, x0, lsl #3] add x0, x0, #0x1 cmp x1, x0 b.ne 400a00 <main._omp_fn.4+0x54> ldr x19, [sp, #16] ldp x29, x30, [sp], #32 ret It can be seen that the vector register (X0) is used before the modification, and the common register (D0) is used after the modification.
next reply other threads:[~2023-05-29 15:14 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-29 15:14 d_vampile at 163 dot com [this message] 2023-05-29 15:17 ` [Bug tree-optimization/110026] " jakub at gcc dot gnu.org 2023-05-30 14:37 ` [Bug target/110026] " d_vampile at 163 dot com 2023-05-30 14:48 ` 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-110026-4@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).