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 middle-end/110148] [14 Regression] TSVC s242 regression between g:c0df96b3cda5738afbba3a65bb054183c5cd5530 and g:e4c986fde56a6248f8fbe6cf0704e1da34b055d8 Date: Sun, 25 Jun 2023 05:56:04 +0000 [thread overview] Message-ID: <bug-110148-4-CvRznp1kAJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110148-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110148 --- Comment #3 from cuilili <lili.cui at intel dot com> --- I reproduced S1244 regression on znver3. Src code: for (int i = 0; i < LEN_1D-1; i++) { a[i] = b[i] + c[i] * c[i] + b[i] * b[i] + c[i]; d[i] = a[i] + a[i+1]; } -------------------------------------------------------- Base version: Base + commit version: Assembler Assembler Loop1: Loop1: vmovsd 0x60c400(%rax),%xmm2 vmovsd 0x60ba00(%rax),%xmm2 vmovsd 0x60ba00(%rax),%xmm1 vmovsd 0x60c400(%rax),%xmm1 add $0x8,%rax add $0x8,%rax -------------------------------------------------------------------- vaddsd %xmm1,%xmm2,%xmm0 vmovsd %xmm2,%xmm2,%xmm0 vmulsd %xmm2,%xmm2,%xmm2 vfmadd132sd %xmm2,%xmm1,%xmm0 vfmadd132sd %xmm1,%xmm2,%xmm1 vfmadd132sd %xmm1,%xmm2,%xmm1 -------------------------------------------------------------------- vaddsd %xmm1,%xmm0,%xmm0 vaddsd %xmm1,%xmm0,%xmm0 vmovsd %xmm0,0x60cdf8(%rax) vmovsd %xmm0,0x60cdf8(%rax) vaddsd 0x60ce00(%rax),%xmm0,%xmm0 vaddsd 0x60ce00(%rax),%xmm0,%xmm0 vmovsd %xmm0,0x60aff8(%rax) vmovsd %xmm0,0x60aff8(%rax) cmp $0x9f8,%rax cmp $0x9f8,%rax jne Loop1: jne Loop1 For the Base version, mult and FMA have dependencies, which increases the latency of the critical dependency chain. I didn't find out why znver3 has regression. Same binary running on ICX has 11% gain (with #define iterations 100000000).
next prev parent reply other threads:[~2023-06-25 5:56 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-06 20:33 [Bug middle-end/110148] New: " hubicka at gcc dot gnu.org 2023-06-06 21:02 ` [Bug middle-end/110148] " pinskia at gcc dot gnu.org 2023-06-09 6:36 ` [Bug middle-end/110148] [14 Regression] " rguenth at gcc dot gnu.org 2023-06-09 11:11 ` lili.cui at intel dot com 2023-06-25 5:56 ` lili.cui at intel dot com [this message] 2023-06-25 20:01 ` hubicka at gcc dot gnu.org 2023-06-29 9:31 ` cvs-commit at gcc dot gnu.org 2023-09-23 10:32 ` jamborm at gcc dot gnu.org 2023-09-26 1:55 ` lili.cui at intel dot com 2023-09-26 15:04 ` jamborm 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-110148-4-CvRznp1kAJ@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).