public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/94863] Failure to use blendps over mov when possible
Date: Thu, 30 Apr 2020 06:57:19 +0000	[thread overview]
Message-ID: <bug-94863-4-RYqxf3bEoG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94863-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
throughputs put aside - how's port allocation and latency figures?  That said,
GCC usually sides on the smaller insn encoding variant when latency isn't
different - we're usually not looking at throughput since throughput figures
are quite useless if you look at single insns (and our decision is per
individual instruction).  Somehow modeling alternatives during scheduling
might make more sense but that's not implemented.

  parent reply	other threads:[~2020-04-30  6:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29 21:54 [Bug rtl-optimization/94863] New: " gabravier at gmail dot com
2020-04-29 22:05 ` [Bug rtl-optimization/94863] " gabravier at gmail dot com
2020-04-30  6:57 ` rguenth at gcc dot gnu.org [this message]
2020-04-30  7:52 ` [Bug target/94863] " gabravier at gmail dot com
2021-04-26  1:18 ` pinskia at gcc dot gnu.org
2024-04-14  2:28 ` pinskia 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-94863-4-RYqxf3bEoG@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).