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 02:52:25 +0000 [thread overview] Message-ID: <bug-103897-4-yewH8a5IML@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 #3 from Hongtao.liu <crazylht at gmail dot com> --- For 1), we have (define_insn "*sse4_1_<code>v4hiv4si2<mask_name>_1" [(set (match_operand:V4SI 0 "register_operand" "=Yr,*x,v") (any_extend:V4SI (match_operand:V4HI 1 "memory_operand" "m,m,m")))] and Failed to match this instruction (set (reg:V4SI 88) (sign_extend:V4SI (vec_select:V4HI (mem:V8HI (reg:DI 91) [0 *src_3(D)+0 S16 A128]) (parallel [ (const_int 0 [0]) (const_int 1 [0x1]) (const_int 2 [0x2]) (const_int 3 [0x3]) ])))) I doubt the optimization is unsafe since there could be trap in 16-byte load, but ok for 8-byte load.
next prev parent reply other threads:[~2022-01-04 2:52 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 ` crazylht at gmail dot com [this message] 2022-01-04 3:08 ` [Bug target/103897] " crazylht 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-103897-4-yewH8a5IML@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: linkBe 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).