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/29256] [11/12/13/14 regression] loop performance regression
Date: Mon, 17 Jul 2023 08:29:50 +0000 [thread overview]
Message-ID: <bug-29256-4-5DPE3KoJJ6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-29256-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29256
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #76 from Richard Biener <rguenth at gcc dot gnu.org> ---
x86_64 has
<bb 3> [local count: 536870800]:
# ivtmp.13_3 = PHI <ivtmp.13_9(3), 0(2)>
vect__1.6_12 = MEM <vector(2) double> [(double *)&a + ivtmp.13_3 * 1];
MEM <vector(2) double> [(double *)&c + ivtmp.13_3 * 1] = vect__1.6_12;
ivtmp.13_9 = ivtmp.13_3 + 16;
if (ivtmp.13_9 != 16000000)
and
.L2:
movapd a(%rax), %xmm0
addq $16, %rax
movaps %xmm0, c-16(%rax)
cmpq $16000000, %rax
jne .L2
which I think is optimal. With -fPIC we get
.L2:
movapd (%rax,%rdx), %xmm0
addq $16, %rax
movaps %xmm0, -16(%rax,%rcx)
cmpq $16000000, %rax
jne .L2
let's close this.
prev parent reply other threads:[~2023-07-17 8:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-29256-4@http.gcc.gnu.org/bugzilla/>
2011-06-27 13:58 ` [Bug middle-end/29256] [4.3/4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-01-12 12:28 ` [Bug target/29256] [4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-03-13 14:23 ` [Bug target/29256] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org
2012-07-02 12:25 ` rguenth at gcc dot gnu.org
2013-04-12 15:17 ` [Bug target/29256] [4.7/4.8/4.9 " jakub at gcc dot gnu.org
2013-12-09 4:50 ` law at redhat dot com
2014-06-12 13:45 ` [Bug target/29256] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:28 ` [Bug target/29256] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-04-07 17:36 ` law at redhat dot com
2015-04-08 7:20 ` rguenther at suse dot de
2015-05-19 17:51 ` [Bug target/29256] [4.8/4.9/5/6 " law at redhat dot com
2015-05-20 2:21 ` amker at gcc dot gnu.org
2015-05-20 12:45 ` wschmidt at gcc dot gnu.org
2015-06-23 8:22 ` rguenth at gcc dot gnu.org
2015-06-26 19:59 ` [Bug target/29256] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:29 ` jakub at gcc dot gnu.org
2015-08-11 18:36 ` wschmidt at gcc dot gnu.org
2015-08-12 7:12 ` rguenther at suse dot de
2015-08-12 7:34 ` amker at gcc dot gnu.org
2015-08-12 13:24 ` wschmidt at gcc dot gnu.org
2015-08-13 2:11 ` amker at gcc dot gnu.org
2015-08-13 3:28 ` wschmidt at gcc dot gnu.org
2015-08-13 5:01 ` amker at gcc dot gnu.org
2021-05-14 9:45 ` [Bug target/29256] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01 8:04 ` rguenth at gcc dot gnu.org
2022-05-27 9:33 ` [Bug target/29256] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:29 ` jakub at gcc dot gnu.org
2023-07-07 10:28 ` [Bug target/29256] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-07-15 7:57 ` pinskia at gcc dot gnu.org
2023-07-17 8:29 ` rguenth at gcc dot gnu.org [this message]
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-29256-4-5DPE3KoJJ6@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: link
Be 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).