public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "colin.king at intel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115069] New: 8 bit integer vector performance regression, x86, between gcc-14 and gcc-13 using avx2 target clones on skylake platform Date: Mon, 13 May 2024 13:05:56 +0000 [thread overview] Message-ID: <bug-115069-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115069 Bug ID: 115069 Summary: 8 bit integer vector performance regression, x86, between gcc-14 and gcc-13 using avx2 target clones on skylake platform Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: colin.king at intel dot com Target Milestone: --- Created attachment 58188 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58188&action=edit reproducer source code I'm seeing a ~12-14% performance regression in gcc-14 compared to gcc-13, using gcc on Ubuntu 24.04: Versions: gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu4) gcc version 14.0.1 20240412 (experimental) [master r14-9935-g67e1433a94f] (Ubuntu 14-20240412-0ubuntu1) cking@skylake:~$ gcc-13 reproducer-vecmath.c -O2 cking@skylake:~$ ./a.out 13540.16 vec8 ops per sec, duration = 14.77 secs cking@skylake:~$ gcc-14 reproducer-vecmath.c -O2 cking@skylake:~$ ./a.out 11720.25 vec8 ops per sec, duration = 17.06 secs The original issue appeared when regression testing stress-ng vecmath stressor [1]. I've managed to extract the attached reproducer from the original code (see attached). Salient point to focus on: 1. The issue is also dependant on the TARGET_CLONES macro being defined as __attribute__((target_clones("mmx,avx,avx2,default"))) - the avx2 target clones seems to be an issue in reproducing this problem, remove it for gcc-14 and the performance regression is reduced. Attached are the reproducer C source and disassembled object code. References: [1] https://github.com/ColinIanKing/stress-ng/blob/master/stress-vecmath.c
next reply other threads:[~2024-05-13 13:05 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-13 13:05 colin.king at intel dot com [this message] 2024-05-13 13:07 ` [Bug target/115069] " colin.king at intel dot com 2024-05-13 13:07 ` colin.king at intel dot com 2024-05-15 8:51 ` haochen.jiang at intel dot com 2024-05-16 1:49 ` [Bug target/115069] [14/15 regression] " sjames at gcc dot gnu.org 2024-05-17 6:59 ` kkanas at fastmail dot com 2024-05-17 7:06 ` liuhongt at gcc dot gnu.org 2024-05-17 7:08 ` haochen.jiang at intel dot com 2024-05-17 8:26 ` ubizjak at gmail dot com 2024-05-17 8:41 ` ubizjak at gmail dot com 2024-05-17 8:48 ` ubizjak at gmail dot com 2024-05-17 9:13 ` haochen.jiang at intel dot com 2024-05-20 1:23 ` liuhongt at gcc dot gnu.org 2024-05-20 5:50 ` haochen.jiang at intel dot com 2024-05-20 6:27 ` ubizjak at gmail dot com 2024-05-20 6:35 ` liuhongt at gcc dot gnu.org 2024-05-20 6:38 ` haochen.jiang at intel dot com 2024-05-20 6:40 ` liuhongt at gcc dot gnu.org 2024-05-20 6:47 ` ubizjak at gmail dot com 2024-05-21 5:56 ` haochen.jiang at intel dot com 2024-05-21 5:58 ` haochen.jiang at intel dot com 2024-05-22 2:25 ` cvs-commit at gcc dot gnu.org 2024-05-22 2:27 ` cvs-commit at gcc dot gnu.org 2024-05-22 2:27 ` haochen.jiang at intel dot com 2024-05-22 5:13 ` liuhongt 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-115069-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).