public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Uros Bizjak <ubizjak@gmail.com>
To: Richard Biener <rguenther@suse.de>
Cc: Jakub Jelinek <jakub@redhat.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][RFC][x86] Fix PR91154, add SImode smax, allow SImode add in SSE regs
Date: Mon, 05 Aug 2019 13:09:00 -0000	[thread overview]
Message-ID: <CAFULd4aw28wMqsW06Pnq89TsfmoqW25tGnzi23Ss3itMe5XDbg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1908051501550.19626@zhemvz.fhfr.qr>

On Mon, Aug 5, 2019 at 3:04 PM Richard Biener <rguenther@suse.de> wrote:
>
> On Mon, 5 Aug 2019, Uros Bizjak wrote:
>
> > On Mon, Aug 5, 2019 at 2:54 PM Jakub Jelinek <jakub@redhat.com> wrote:
> > >
> > > On Mon, Aug 05, 2019 at 02:51:01PM +0200, Uros Bizjak wrote:
> > > > > (define_mode_iterator MAXMIN_IMODE [SI "TARGET_SSE4_1"] [DI "TARGET_AVX512F"])
> > > > >
> > > > > and then we need to split DImode for 32bits, too.
> > > >
> > > > For now, please add "TARGET_64BIT && TARGET_AVX512F" for DImode
> > > > condition, I'll provide _doubleword splitter later.
> > >
> > > Shouldn't that be TARGET_AVX512VL instead?  Or does the insn use %g0 etc.
> > > to force use of %zmmN?
> >
> > It generates V4SI mode, so - yes, AVX512VL.
>
>     case SMAX:
>     case SMIN:
>     case UMAX:
>     case UMIN:
>       if ((mode == DImode && (!TARGET_64BIT || !TARGET_AVX512VL))
>           || (mode == SImode && !TARGET_SSE4_1))
>         return false;
>
> so there's no way to use AVX512VL for 32bit?

There is a way, but on 32bit targets, we need to split DImode
operation to a sequence of SImode operations for unconverted pattern.
This is of course doable, but somehow more complex than simply
emitting a DImode compare + DImode cmove, which is what current
splitter does. So, a follow-up task.

Uros.

  reply	other threads:[~2019-08-05 13:09 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-23 14:03 Richard Biener
2019-07-24  9:14 ` Richard Biener
2019-07-24 11:30   ` Richard Biener
2019-07-24 15:12 ` Jeff Law
2019-07-27 10:07   ` Uros Bizjak
2019-08-09 22:15     ` Jeff Law
2019-07-25  9:15 ` Martin Jambor
2019-07-25 12:57   ` Richard Biener
2019-07-27 11:14     ` Uros Bizjak
2019-07-27 18:23       ` Uros Bizjak
2019-07-31 12:01         ` Richard Biener
2019-08-01  8:54           ` Uros Bizjak
2019-08-01  9:28             ` Richard Biener
2019-08-01  9:38               ` Uros Bizjak
2019-08-03 17:26                 ` Richard Biener
2019-08-04 17:11                   ` Uros Bizjak
2019-08-04 17:23                     ` Jakub Jelinek
2019-08-04 17:36                       ` Uros Bizjak
2019-08-05  8:47                         ` Richard Biener
2019-08-05  9:13                     ` Richard Sandiford
2019-08-05 10:08                       ` Uros Bizjak
2019-08-05 10:12                         ` Richard Sandiford
2019-08-05 10:24                           ` Uros Bizjak
2019-08-05 10:39                             ` Richard Sandiford
2019-08-05 11:50                     ` Richard Biener
2019-08-05 11:59                       ` Uros Bizjak
2019-08-05 12:16                         ` Richard Biener
2019-08-05 12:23                           ` Uros Bizjak
2019-08-05 12:33                       ` Uros Bizjak
2019-08-08 16:23                         ` Jeff Law
2019-08-05 12:44                       ` Uros Bizjak
2019-08-05 12:51                         ` Uros Bizjak
2019-08-05 12:54                           ` Jakub Jelinek
2019-08-05 12:57                             ` Uros Bizjak
2019-08-05 13:04                               ` Richard Biener
2019-08-05 13:09                                 ` Uros Bizjak [this message]
2019-08-05 13:29                                   ` Richard Biener
2019-08-05 19:35                                     ` Uros Bizjak
2019-08-07  9:52                                       ` Richard Biener
2019-08-07 12:04                                         ` Richard Biener
2019-08-07 12:11                                           ` Uros Bizjak
2019-08-07 12:42                                           ` Uros Bizjak
2019-08-07 12:58                                             ` Uros Bizjak
2019-08-07 13:00                                               ` Richard Biener
2019-08-07 13:32                                                 ` Uros Bizjak
2019-08-07 14:15                                         ` Richard Biener
2019-08-09  7:28                                   ` Uros Bizjak
2019-08-09 10:13                                     ` Richard Biener
2019-08-09 10:26                                       ` Jakub Jelinek
2019-08-09 11:15                                         ` Richard Biener
2019-08-09 11:06                                       ` Richard Biener
2019-08-09 13:13                                         ` Richard Biener
2019-08-09 14:39                                           ` Uros Bizjak
2019-08-12 12:57                                             ` Richard Biener
2019-08-12 14:48                                               ` Uros Bizjak
2019-08-13 16:28                                               ` Jeff Law
2019-08-13 20:07                                                 ` H.J. Lu
2019-08-15  9:24                                                   ` Uros Bizjak
2019-08-13 15:20                                           ` Jeff Law
2019-08-14  9:15                                             ` Richard Biener
2019-08-14  9:36                                               ` 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=CAFULd4aw28wMqsW06Pnq89TsfmoqW25tGnzi23Ss3itMe5XDbg@mail.gmail.com \
    --to=ubizjak@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=rguenther@suse.de \
    /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).