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/110762] inappropriate use of SSE (or AVX) insns for v2sf mode operations
Date: Fri, 21 Jul 2023 09:19:34 +0000	[thread overview]
Message-ID: <bug-110762-4-1EUd4DSqhi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110762-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |wrong-code
   Last reconfirmed|                            |2023-07-21
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
The

   (insn 13 4 14 2 (set (reg:V2SF 20 xmm0 [orig:91 x2 ] [91])
        (vec_select:V2SF (reg:V4SF 20 xmm0 [94])
            (parallel [
                    (const_int 0 [0])
                    (const_int 1 [0x1])
                ]))) "t.c":10:12 4394 {sse_storelps}
     (nil))

insns are gone in split after reload.

  parent reply	other threads:[~2023-07-21  9:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21  8:43 [Bug target/110762] New: " jbeulich at suse dot com
2023-07-21  9:13 ` [Bug target/110762] " rguenth at gcc dot gnu.org
2023-07-21  9:19 ` rguenth at gcc dot gnu.org [this message]
2023-07-21  9:36 ` ubizjak at gmail dot com
2023-07-21  9:40 ` amonakov at gcc dot gnu.org
2023-07-21 10:22 ` segher at gcc dot gnu.org
2023-07-21 10:46 ` rguenth at gcc dot gnu.org
2023-07-21 10:47 ` rguenth at gcc dot gnu.org
2023-07-21 10:49 ` rguenth at gcc dot gnu.org
2023-07-21 10:53 ` jbeulich at suse dot com
2023-07-21 11:09 ` ubizjak at gmail dot com
2023-07-21 11:16 ` rguenth at gcc dot gnu.org
2023-07-21 11:25 ` rguenth at gcc dot gnu.org
2023-07-21 12:42 ` ubizjak at gmail dot com
2023-07-21 12:47 ` amonakov at gcc dot gnu.org
2023-07-21 13:18 ` jbeulich at suse dot com
2023-07-26  7:30 ` ubizjak at gmail dot com
2023-07-26  7:53 ` rguenth at gcc dot gnu.org
2023-07-26  9:34 ` ubizjak at gmail dot com
2023-07-26 10:18 ` cvs-commit at gcc dot gnu.org
2023-07-28  6:28 ` [Bug target/110762] [11/12/13 Regression] " rguenth at gcc dot gnu.org
2023-07-28  8:15 ` ubizjak at gmail dot com
2023-07-31  8:04 ` ubizjak at gmail dot com
2023-07-31  8:10 ` crazylht at gmail dot com
2023-08-07 11:52 ` cvs-commit at gcc dot gnu.org
2023-08-25  9:04 ` 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-110762-4-1EUd4DSqhi@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).