public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lili.cui at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104723] [12 regression] Redundant usage of stack
Date: Wed, 02 Mar 2022 08:11:56 +0000 [thread overview]
Message-ID: <bug-104723-4-lz4xcFzbc8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104723-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104723
--- Comment #9 from cuilili <lili.cui at intel dot com> ---
(In reply to cuilili from comment #3)
> (In reply to Hongtao.liu from comment #1)
> > STF issue here?
>
correct comment #3
I used perf to collect the "ld_blocks.store_forward" event for those two test
cases, stlf_64_55_64.S has STLF issue due to the two stores overlapping, not
related to crossing cache line.
In this case it has STLF issue.
----------------------------------------------------------------
$cat stlf_64_55_64.S
...
.LFB0:
.cfi_startproc
vmovdqu %ymm0, -64(%rsp)
vmovdqu %ymm1, -55(%rsp)
vmovdqu -64(%rsp), %ymm0
ret
.cfi_endproc
...
$ perf stat -e ld_blocks.store_forward ./stlf_64_55_64.out
runtime= : 128883744
Performance counter stats for './stlf_64_55_64.out':
10,000,507 ld_blocks.store_forward:u
----------------------------------------------------------------
In this case it can do STLF.
----------------------------------------------------------------
$ cat stlf_64_128_64.S
...
.LFB0:
.cfi_startproc
vmovdqu %ymm0, -64(%rsp)
vmovdqu %ymm1, -128(%rsp)
vmovdqu -64(%rsp), %ymm0
ret
.cfi_endproc
...
$ perf stat -e ld_blocks.store_forward ./stlf_64_128_64.out
runtime= : 56477424
Performance counter stats for './stlf_64_128_64.out':
2 ld_blocks.store_forward:u
0.022103902 seconds time elapsed
-------------------------------------------------------------
next prev parent reply other threads:[~2022-03-02 8:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 8:35 [Bug target/104723] New: " crazylht at gmail dot com
2022-03-01 8:44 ` [Bug target/104723] " crazylht at gmail dot com
2022-03-01 8:47 ` crazylht at gmail dot com
2022-03-01 12:38 ` lili.cui at intel dot com
2022-03-01 13:41 ` rguenth at gcc dot gnu.org
2022-03-01 16:00 ` jakub at gcc dot gnu.org
2022-03-01 16:07 ` jakub at gcc dot gnu.org
2022-03-01 18:45 ` hjl.tools at gmail dot com
2022-03-01 18:50 ` hjl.tools at gmail dot com
2022-03-02 8:11 ` lili.cui at intel dot com [this message]
2022-04-22 16:28 ` jakub at gcc dot gnu.org
2022-04-24 7:37 ` lili.cui at intel dot com
2022-04-26 9:41 ` jakub at gcc dot gnu.org
2022-05-06 8:32 ` [Bug target/104723] [12/13 " jakub at gcc dot gnu.org
2022-07-26 12:58 ` rguenth at gcc dot gnu.org
2023-05-08 12:23 ` [Bug target/104723] [12/13/14 " 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-104723-4-lz4xcFzbc8@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).