public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Cc: richard.sandiford <richard.sandiford@arm.com>,
	 rguenther <rguenther@suse.de>
Subject: [PATCH] IFN: Fix vector extraction into promoted subreg.
Date: Wed, 16 Aug 2023 09:31:44 +0800	[thread overview]
Message-ID: <A5B5119E73867E8D+2023081609314414050517@rivai.ai> (raw)

[-- Attachment #1: Type: text/plain, Size: 411 bytes --]

Hi, Robin, Richard and Richi.

I am wondering whether we can just simply replace the VEC_EXTRACT expander with binary?

Like this :?

DEF_INTERNAL_OPTAB_FN (VEC_EXTRACT, ECF_CONST | ECF_NOTHROW,
-          vec_extract, vec_extract)
+          vec_extract, binary)

to fix the sign extend issue.

And remove the vec_extract explicit expander in internal-fn.cc ?

Thanks.


juzhe.zhong@rivai.ai

             reply	other threads:[~2023-08-16  1:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16  1:31 juzhe.zhong [this message]
2023-08-16  6:45 ` Richard Sandiford
2023-08-16  9:37   ` Robin Dapp
2023-08-16 10:05     ` Richard Sandiford
  -- strict thread matches above, loose matches on Subject: below --
2023-08-15 14:02 Robin Dapp

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=A5B5119E73867E8D+2023081609314414050517@rivai.ai \
    --to=juzhe.zhong@rivai.ai \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.de \
    --cc=richard.sandiford@arm.com \
    /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).