public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111064] 5-10% regression of parest on icelake between g:d073e2d75d9ed492de9a8dc6970e5b69fae20e5a (Aug 15 2023) and g:9ade70bb86c8744f4416a48bb69cf4705f00905a (Aug 16)
Date: Tue, 29 Aug 2023 06:22:09 +0000	[thread overview]
Message-ID: <bug-111064-4-A9FP2Pcah3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111064-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Hongtao.liu <crazylht at gmail dot com> ---

> 
> [liuhongt@intel gather_emulation]$ ./gather.out
> ;./nogather_xmm.out;./nogather_ymm.out
> elapsed time: 1.75997 seconds for gather with 30000000 iterations
> elapsed time: 2.42473 seconds for no_gather_xmm with 30000000 iterations
> elapsed time: 1.86436 seconds for no_gather_ymm with 30000000 iterations
> 


For 510.parest_r, enable gather emulation for ymm can bring back 3%
performance, still not as good as gather instruction due to thoughput bound.

      parent reply	other threads:[~2023-08-29  6:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18 11:48 [Bug target/111064] New: " hubicka at gcc dot gnu.org
2023-08-18 12:39 ` [Bug target/111064] " hubicka at gcc dot gnu.org
2023-08-18 13:24 ` rguenth at gcc dot gnu.org
2023-08-22  2:54 ` crazylht at gmail dot com
2023-08-25  6:02 ` crazylht at gmail dot com
2023-08-25  8:16 ` fkastl at suse dot cz
2023-08-29  6:22 ` crazylht at gmail dot com [this message]

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-111064-4-A9FP2Pcah3@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).