From: Uros Bizjak <ubizjak@gmail.com>
To: Roger Sayle <roger@nextmovesoftware.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"H. J. Lu" <hjl.tools@gmail.com>
Subject: Re: [x86_64 PATCH] Improved Scalar-To-Vector (STV) support for TImode to V1TImode.
Date: Mon, 11 Jul 2022 08:41:32 +0200 [thread overview]
Message-ID: <CAFULd4bvSbKfLn-=08qNA17SgNa4-i7uS=3N19456pTP-eXx7g@mail.gmail.com> (raw)
In-Reply-To: <00f201d8948b$ec82a6e0$c587f4a0$@nextmovesoftware.com>
On Sun, Jul 10, 2022 at 8:36 PM Roger Sayle <roger@nextmovesoftware.com> wrote:
>
>
> Hi Uros,
> Yes, I agree. I think it makes sense to have a single STV pass (after
> combine and before reload). Let's hear what HJ thinks, but I'm
> happy to investigate a follow-up patch that unifies the STV passes.
> But it'll be easier to confirm there are no "code generation" changes
> if those modifications are pushed independently of these ones.
> Time to look into the (git) history of multiple STV passes...
OK, let's go forward with the proposed patch.
Thanks,
Uros.
prev parent reply other threads:[~2022-07-11 6:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 12:17 Roger Sayle
2022-07-10 18:05 ` Uros Bizjak
2022-07-10 18:36 ` Roger Sayle
2022-07-10 19:15 ` H.J. Lu
2022-07-10 21:38 ` Roger Sayle
2022-07-10 23:56 ` H.J. Lu
2022-07-14 5:31 ` Roger Sayle
2022-07-14 7:10 ` Richard Biener
2022-07-11 6:41 ` Uros Bizjak [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='CAFULd4bvSbKfLn-=08qNA17SgNa4-i7uS=3N19456pTP-eXx7g@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=roger@nextmovesoftware.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).