public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robin Dapp <rdapp@linux.ibm.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>, ubizjak@gmail.com
Subject: optabs: Variable index vec_set
Date: Mon, 31 Oct 2022 16:42:56 +0100	[thread overview]
Message-ID: <546be11b-5bb6-e312-e309-291787d25018@linux.ibm.com> (raw)

Hi,

I'm looking into vec_set with variable index on s390.  Uros posted a
patch [1] that did not make it upstream in Nov 2020.  It changed the
mode of the index operand to whatever the target supports in
can_vec_set_var_idx_p.  I missed it back then but we indeed do not make
proper use of vec_set with an index register.

With the patch my local changes to make better use of vec_set work
nicely even though I haven't done a full bootstrap yet.  Were there
other issues with the patch or can it still be applied?

Regards
 Robin

[1]
https://gcc.gnu.org/pipermail/gcc-patches/2020-November/559213.html

             reply	other threads:[~2022-10-31 15:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 15:42 Robin Dapp [this message]
2022-11-02 12:12 ` Robin Dapp
2022-11-02 12:39   ` Uros Bizjak
2022-11-02 12:45     ` Robin Dapp
2022-11-02 12:46       ` Uros Bizjak
2022-11-05 11:25         ` Richard Biener
2022-11-06 19:53           ` Uros Bizjak

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=546be11b-5bb6-e312-e309-291787d25018@linux.ibm.com \
    --to=rdapp@linux.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ubizjak@gmail.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).