public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "haochen.jiang at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/115069] [14/15 regression] 8 bit integer vector performance regression, x86, between gcc-14 and gcc-13 using avx2 target clones on skylake platform
Date: Fri, 17 May 2024 07:08:50 +0000	[thread overview]
Message-ID: <bug-115069-4-gJJQsP8Lv7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115069-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115069

--- Comment #6 from Haochen Jiang <haochen.jiang at intel dot com> ---
(In reply to Hongtao Liu from comment #5)
> (In reply to Krzysztof Kanas from comment #4)
> > I bisected the issue and it seems that commit
> > 0368fc54bc11f15bfa0ed9913fd0017815dfaa5d introduces regression.
> 
> I guess the real guilty commit is 
> 
> commit 52ff3f7b863da1011b73c0ab3b11f6c78b6451c7
> Author: Uros Bizjak <ubizjak@gmail.com>
> Date:   Thu May 25 19:40:26 2023 +0200
>  
>     i386: Use 2x-wider modes when emulating QImode vector instructions
>  
>     Rewrite ix86_expand_vecop_qihi2 to expand fo 2x-wider (e.g. V16QI ->
> V16HImode)
>     instructions when available.  Currently, the compiler generates following
>     assembly for V16QImode multiplication (-mavx2):

Yes, since 0368fc54bc11f15bfa0ed9913fd0017815dfaa5d only fixed a typo in that
patch.

Original thread: https://gcc.gnu.org/pipermail/gcc-patches/2023-May/619745.html

  parent reply	other threads:[~2024-05-17  7:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13 13:05 [Bug target/115069] New: " colin.king at intel dot com
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 [this message]
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-gJJQsP8Lv7@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).