public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108764] [RISCV] Cost model for RVB is too aggressive
Date: Sun, 12 Feb 2023 08:22:22 +0000	[thread overview]
Message-ID: <bug-108764-4-uuxVvDTb8w@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108764-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
        slli    a4,a2,3
        sh3add  a5,a2,a0

vs
        slli    a2,a2,3
        add     a5,a0,a2

I think the first one is better really because you have two indepedent
instructions and can be issued at the same time.
Really this is all core specific and the generic tuning should be "generic"
which means this is the correct tuning ...

  parent reply	other threads:[~2023-02-12  8:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-12  7:36 [Bug target/108764] New: " sinan.lin at linux dot alibaba.com
2023-02-12  7:46 ` [Bug target/108764] " sinan.lin at linux dot alibaba.com
2023-02-12  8:22 ` pinskia at gcc dot gnu.org [this message]
2023-02-12 10:08 ` kito at gcc dot gnu.org
2023-02-12 10:47 ` sinan.lin at linux dot alibaba.com
2023-02-12 11:00 ` sinan.lin at linux dot alibaba.com
2023-02-22  2:26 ` law 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-108764-4-uuxVvDTb8w@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).