public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110832] [14 Regression] 14% capacita -O2 regression between g:9fdbd7d6fa5e0a76 (2023-07-26 01:45) and g:ca912a39cccdd990 (2023-07-27 03:44) on zen3 and core
Date: Mon, 31 Jul 2023 07:54:17 +0000	[thread overview]
Message-ID: <bug-110832-4-dJbVhmXodt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110832-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Hongtao.liu from comment #9)
> for mov<mode>_internal, we can just set alternative (v,v) with mode DI, then
> it will use vmovq, for other alternatives which set sse_regs, the
> instructions has already cleared the upper bits.
Move instructions can be sanitized in ix86_expand_vector_move. If the target is
in V2SFmode and the source is a subreg register, then movq_v2sf_to_sse should
be emitted. However, we would still like to emit MOVAPS reg, reg for V2SF to
V2SF moves, because MOVAPS may be eliminated by hardware, while MOVQ won't be.

  parent reply	other threads:[~2023-07-31  7:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27 17:27 [Bug middle-end/110832] New: " hubicka at gcc dot gnu.org
2023-07-27 17:28 ` [Bug middle-end/110832] " hubicka at gcc dot gnu.org
2023-07-27 18:35 ` hubicka at ucw dot cz
2023-07-28  6:21 ` rguenth at gcc dot gnu.org
2023-07-28  6:21 ` [Bug middle-end/110832] [14 Regression] " rguenth at gcc dot gnu.org
2023-07-28 12:30 ` ubizjak at gmail dot com
2023-07-28 12:36 ` ubizjak at gmail dot com
2023-07-28 13:28 ` rguenth at gcc dot gnu.org
2023-07-28 13:41 ` ubizjak at gmail dot com
2023-07-28 15:46 ` ubizjak at gmail dot com
2023-07-31  4:58 ` crazylht at gmail dot com
2023-07-31  7:54 ` ubizjak at gmail dot com [this message]
2023-08-08 16:56 ` cvs-commit at gcc dot gnu.org
2023-08-09  9:46 ` ubizjak at gmail dot com
2023-08-10  6:06 ` cvs-commit at gcc dot gnu.org
2023-08-25  8:59 ` ubizjak at gmail dot com

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-110832-4-dJbVhmXodt@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).