From: Uros Bizjak <ubizjak@gmail.com>
To: Hongtao Liu <crazylht@gmail.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
Roger Sayle <roger@nextmovesoftware.com>,
liuhongt <hongtao.liu@intel.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Expand __builtin_memcmp_eq with ptest for OI/TImode.
Date: Thu, 5 May 2022 10:30:03 +0200 [thread overview]
Message-ID: <CAFULd4bOQbsiDhHMvQWLW2SK2vh-kT5qY4fjJDy2cAikGp-YfA@mail.gmail.com> (raw)
In-Reply-To: <CAMZc-bxf4iEZ=r1qz1ut4N4LyMu--Mp61V+GN4b8cKfsHW2N4Q@mail.gmail.com>
On Thu, May 5, 2022 at 10:23 AM Hongtao Liu <crazylht@gmail.com> wrote:
>
> On Thu, May 5, 2022 at 4:09 PM Uros Bizjak via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
> >
> > On Thu, May 5, 2022 at 9:50 AM Richard Biener via Gcc-patches
> > <gcc-patches@gcc.gnu.org> wrote:
> > >
> > > On Thu, May 5, 2022 at 9:37 AM liuhongt via Gcc-patches
> > > <gcc-patches@gcc.gnu.org> wrote:
> > > >
> > > > Enable optimization for TImode only under 32-bit target, for 64-bit
> > > > target there could be extra ineteger <-> sse move regarding psABI,
> > > > not efficient.
> > > >
> > > > Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}
> > > > Ok for trunk?
> > >
> > > I wonder if this is better done in STV where we could assess this extra cost?
> >
> > Yes, this should be handled via STV, Roger Sayle (CC'd) has proposed a
> > patch that does just that.
> >
> My patch also handles OImode, I think that part could be a separate patch.
Yes, OImode (and TImode on x86_32) can't be implemented using integer registers.
Uros,
next prev parent reply other threads:[~2022-05-05 8:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 7:37 liuhongt
2022-05-05 7:37 ` Hongtao Liu
2022-05-05 7:49 ` Richard Biener
2022-05-05 8:08 ` Uros Bizjak
2022-05-05 8:21 ` Uros Bizjak
2022-05-05 8:22 ` Hongtao Liu
2022-05-05 8:30 ` Uros Bizjak [this message]
2022-05-07 5:05 ` [PATCH] Expand __builtin_memcmp_eq with ptest for OImode liuhongt
2022-05-09 0:57 ` Hongtao Liu
2022-05-16 1:47 ` Hongtao Liu
2022-05-16 9:10 ` Uros Bizjak
2022-05-17 1:33 ` Hongtao Liu
2022-05-17 10:03 ` Uros Bizjak
2022-05-18 2:53 ` Hongtao Liu
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=CAFULd4bOQbsiDhHMvQWLW2SK2vh-kT5qY4fjJDy2cAikGp-YfA@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=crazylht@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hongtao.liu@intel.com \
--cc=richard.guenther@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).