public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pan2.li at intel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113247] RISC-V: Performance bug in SHA256 after enabling RVV vectorization Date: Thu, 11 Jan 2024 01:37:42 +0000 [thread overview] Message-ID: <bug-113247-4-K4TmYjWCAL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113247-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113247 --- Comment #10 from Li Pan <pan2.li at intel dot com> --- (In reply to Robin Dapp from comment #9) > I also noticed this (likely unwanted) vector snippet and wondered where it > is being created. First I thought it's a vec_extract but doesn't look like > it. I'm going to check why we create this. > > Pan, the test was on real hardware I suppose? Yes. > So regardless of the fact > that we likely want to get rid of the snippet above, would you mind checking > whether generic-ooo has any effect on performance? Maybe you could try > -march=rv64gc -mtune=generic-ooo. Thanks. Sure thing, actually I have some performance data that is under review to make sure the alignment to the company policy before share to the community. I will add a new column for generic-ooo.
next prev parent reply other threads:[~2024-01-11 1:37 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-06 0:02 [Bug c/113247] New: RISC-V: Performance bug in SHA256 juzhe.zhong at rivai dot ai 2024-01-09 14:47 ` [Bug target/113247] RISC-V: Performance bug in SHA256 after enabling RVV vectorization rdapp at gcc dot gnu.org 2024-01-09 14:53 ` juzhe.zhong at rivai dot ai 2024-01-09 15:02 ` rdapp at gcc dot gnu.org 2024-01-09 15:15 ` rdapp at gcc dot gnu.org 2024-01-10 0:54 ` juzhe.zhong at rivai dot ai 2024-01-10 6:29 ` juzhe.zhong at rivai dot ai 2024-01-10 10:00 ` juzhe.zhong at rivai dot ai 2024-01-10 12:35 ` pan2.li at intel dot com 2024-01-10 13:41 ` rdapp at gcc dot gnu.org 2024-01-11 1:37 ` pan2.li at intel dot com [this message] 2024-01-15 13:15 ` cvs-commit at gcc dot gnu.org 2024-01-15 13:24 ` juzhe.zhong at rivai dot ai
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-113247-4-K4TmYjWCAL@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).