public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103897] x86: Missing optimizations with _mm_undefined_si128 and PMOVSX*
Date: Tue, 04 Jan 2022 03:08:24 +0000	[thread overview]
Message-ID: <bug-103897-4-YlNk7YXQ9o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103897-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Hongtao.liu <crazylht at gmail dot com> ---
For 2), it seems to be a generic optimization to optimize

(set (mem:V4SI (reg:DI 95) [0 *dst_7(D)+0 S16 A128])
    (ashiftrt:V4SI (subreg:V4SI (vec_select:V8HI (vec_concat:V16HI
(const_vector:V8HI [
                            (const_int 0 [0]) repeated x8
                        ])
                    (mem:V8HI (reg:DI 96) [0 *src_3(D)+0 S16 A128]))
                (parallel [
                        (const_int 0 [0])
                        (const_int 8 [0x8])
                        (const_int 1 [0x1])
                        (const_int 9 [0x9])
                        (const_int 2 [0x2])
                        (const_int 10 [0xa])
                        (const_int 3 [0x3])
                        (const_int 11 [0xb])
                    ])) 0)
        (const_int 16 [0x10])))


to sign_extend of (mem:V8HI (reg:DI 96)

      parent reply	other threads:[~2022-01-04  3:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 11:19 [Bug tree-optimization/103897] New: " nekotekina at gmail dot com
2022-01-03 13:44 ` [Bug tree-optimization/103897] " pinskia at gcc dot gnu.org
2022-01-03 19:20 ` pinskia at gcc dot gnu.org
2022-01-04  2:52 ` [Bug target/103897] " crazylht at gmail dot com
2022-01-04  3:08 ` crazylht at gmail dot com [this message]

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-103897-4-YlNk7YXQ9o@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).