public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: Robin Dapp <rdapp@linux.ibm.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: optabs: Variable index vec_set
Date: Sat, 5 Nov 2022 12:25:16 +0100	[thread overview]
Message-ID: <CAFiYyc0pt3iUyiNdaWJz52ksF1nASGcccsHaDktG57qzYwYaRw@mail.gmail.com> (raw)
In-Reply-To: <CAFULd4aSDhL4ZJRymkJo-OKFnA4HbnADHZCaHk7f6hJDm9iL-A@mail.gmail.com>

On Wed, Nov 2, 2022 at 1:46 PM Uros Bizjak <ubizjak@gmail.com> wrote:
>
> On Wed, Nov 2, 2022 at 1:45 PM Robin Dapp <rdapp@linux.ibm.com> wrote:
> >
> > > IIRC, I was trying to "fix" modeless operand by giving it a mode, but
> > > since it made no difference for x86, I later dropped the patch.
> > > However, operand with a known mode is preferred, so if it works for
> > > you, just include my patch in your submission. My patch is somehow
> > > trivial if we want operand to have known mode.
> >
> > I'd prefer to push it separately as my patch changes several things in
> > the s390 backend that are kind of unrelated.  Is it OK to do an x86
> > bootstrap and regtest and push it if everything looks good?  You can of
> > course also do it yourself :)
>
> It is a middle-end patch, someone will have to approve it.

The patch is OK

> Uros.

  reply	other threads:[~2022-11-05 11:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 15:42 Robin Dapp
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 [this message]
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=CAFiYyc0pt3iUyiNdaWJz52ksF1nASGcccsHaDktG57qzYwYaRw@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rdapp@linux.ibm.com \
    --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).