public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/99411] New: s311 benchmark of TSVC is vectorized by clang better than by gcc Date: Fri, 05 Mar 2021 14:30:55 +0000 [thread overview] Message-ID: <bug-99411-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99411 Bug ID: 99411 Summary: s311 benchmark of TSVC is vectorized by clang better than by gcc Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: hubicka at gcc dot gnu.org Target Milestone: --- typedef float real_t; #define iterations 100000 #define LEN_1D 32000 #define LEN_2D 256 real_t a[LEN_1D]; int main() { // reductions // sum reduction real_t sum; for (int nl = 0; nl < iterations*10; nl++) { sum = (real_t)0.; for (int i = 0; i < LEN_1D; i++) { sum += a[i]; } } return sum > 4; } We produce with -O2 -march=znver2 .L2: movl $a, %eax vxorps %xmm0, %xmm0, %xmm0 .p2align 4 .p2align 3 .L3: vaddps (%rax), %ymm0, %ymm0 addq $32, %rax cmpq $a+128000, %rax jne .L3 vextractf128 $0x1, %ymm0, %xmm1 decl %edx vaddps %xmm0, %xmm1, %xmm1 vmovhlps %xmm1, %xmm1, %xmm0 vaddps %xmm1, %xmm0, %xmm0 vshufps $85, %xmm0, %xmm0, %xmm1 vaddps %xmm0, %xmm1, %xmm0 jne .L2 xorl %eax, %eax vcomiss .LC0(%rip), %xmm0 seta %al vzeroupper ret .cfi_endproc clang does: main: # @main .cfi_startproc # %bb.0: xorl %eax, %eax .p2align 4, 0x90 .LBB0_1: # =>This Loop Header: Depth=1 # Child Loop BB0_2 Depth 2 vxorps %xmm0, %xmm0, %xmm0 movq $-128000, %rcx # imm = 0xFFFE0C00 vxorps %xmm1, %xmm1, %xmm1 vxorps %xmm2, %xmm2, %xmm2 vxorps %xmm3, %xmm3, %xmm3 .p2align 4, 0x90 .LBB0_2: # Parent Loop BB0_1 Depth=1 # => This Inner Loop Header: Depth=2 vaddps a+128000(%rcx), %ymm0, %ymm0 vaddps a+128032(%rcx), %ymm1, %ymm1 vaddps a+128064(%rcx), %ymm2, %ymm2 vaddps a+128096(%rcx), %ymm3, %ymm3 subq $-128, %rcx jne .LBB0_2 # %bb.3: # in Loop: Header=BB0_1 Depth=1 incl %eax cmpl $1000000, %eax # imm = 0xF4240 jne .LBB0_1 # %bb.4: vaddps %ymm0, %ymm1, %ymm0 xorl %eax, %eax vaddps %ymm0, %ymm2, %ymm0 vaddps %ymm0, %ymm3, %ymm0 vextractf128 $1, %ymm0, %xmm1 vaddps %xmm1, %xmm0, %xmm0 vpermilpd $1, %xmm0, %xmm1 # xmm1 = xmm0[1,0] vaddps %xmm1, %xmm0, %xmm0 vmovshdup %xmm0, %xmm1 # xmm1 = xmm0[1,1,3,3] vaddss %xmm1, %xmm0, %xmm0 vucomiss .LCPI0_0(%rip), %xmm0 seta %al vzeroupper retq On zen3 hardware gcc version runs 2.4s, while clang's 0.8s
next reply other threads:[~2021-03-05 14:30 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-05 14:30 hubicka at gcc dot gnu.org [this message] 2021-03-05 14:41 ` [Bug middle-end/99411] s311 and s31111 " hubicka at gcc dot gnu.org 2021-03-05 14:43 ` [Bug middle-end/99411] s311, s312 " hubicka at gcc dot gnu.org 2021-03-05 14:46 ` [Bug middle-end/99411] s311, s312, s31111 " hubicka at gcc dot gnu.org 2021-03-05 14:49 ` [Bug middle-end/99411] s311, s312, s31111 and s31111, s3110 " hubicka at gcc dot gnu.org 2021-03-05 15:03 ` [Bug middle-end/99411] s311, s312, s31111, s31111, s3110, vsumr " hubicka at gcc dot gnu.org 2021-03-08 8:24 ` [Bug tree-optimization/99411] " rguenth at gcc dot gnu.org 2022-11-16 17:16 ` hubicka at gcc dot gnu.org 2023-01-11 22:36 ` hubicka 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-99411-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).