public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Uros Bizjak <ubizjak@gmail.com>
To: Roger Sayle <roger@nextmovesoftware.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [x86 PATCH] Double word implementation of and; cmp to not; test optimization.
Date: Tue, 7 Jun 2022 08:08:03 +0200	[thread overview]
Message-ID: <CAFULd4aM4f_srcAur6p0gb4zWGd7roR+bK5v7qCeAuwS7RgDzg@mail.gmail.com> (raw)
In-Reply-To: <CAFULd4Y_PkGE2+4K=jZ6dVoy15FkE2XfJDRz6qMEfaym=FDeZQ@mail.gmail.com>

On Mon, Jun 6, 2022 at 1:28 PM Uros Bizjak <ubizjak@gmail.com> wrote:
>
> On Sun, Jun 5, 2022 at 7:19 PM Roger Sayle <roger@nextmovesoftware.com> wrote:
> >
> >
> > This patch extends the recent and;cmp to not;test optimization to also
> > perform this transformation for TImode on TARGET_64BIT and DImode on -m32,
> > One motivation for this is that it's a step to fixing the current failure
> > of gcc.target/i386/pr65105-5.c on -m32.
> >
> > A more direct benefit for x86_64 is that the following code:
> >
> > int foo(__int128 x, __int128 y)
> > {
> >   return (x & y) == y;
> > }
> >
> > improves (with -O2 -mbmi) from:
> >
> >         movq    %rdi, %r8
> >         movq    %rsi, %rdi
> >         movq    %rdx, %rsi
> >         andq    %rcx, %rdi
> >         movq    %r8, %rax
> >         andq    %rdx, %rax
> >         movq    %rdi, %rdx
> >         xorq    %rsi, %rax
> >         xorq    %rcx, %rdx
> >         orq     %rdx, %rax
> >         sete    %al
> >         movzbl  %al, %eax
> >         ret
> >
> > to the much better:
> >
> >         movq    %rdi, %r8
> >         movq    %rsi, %rdi
> >         andn    %rdx, %r8, %rax
> >         andn    %rcx, %rdi, %rsi
> >         orq     %rsi, %rax
> >         sete    %al
> >         movzbl  %al, %eax
> >         ret
> >
> > The major theme of this patch is to generalize many of i386.md's
> > *di3_doubleword patterns to become *<dwi>_doubleword patterns, i.e.
> > whenever there exists a "double word" optimization for DImode with -m32,
> > there should be an equivalent TImode optimization on TARGET_64BIT.
> >
> > The following patch has been tested on x86_64-pc-linux-gnu with
> > make bootstrap and make -k check, where on TARGET_64BIT there are
> > no new failures, but paradoxically with --target_board=unix{-m32}
> > the other dg-final clause in gcc.target/i386/pr65105-5.c now fails.
> > Counter-intuitively, this is progress, and pr65105-5.c may now be
> > fixed (without using peephole2) simply by tweaking the STV pass to
> > handle andn/test (in a follow-up patch).
> > OK for mainline?
> >
> >
> > 2022-06-05  Roger Sayle  <roger@nextmovesoftware.com>
> >
> > gcc/ChangeLog
> >         * config/i386/i386.cc (ix86_rtx_costs) <COMPARE>: Provide costs
> >         for double word comparisons and tests (comparisons against zero).
> >         * config/i386/i386.md (*test<mode>_not_doubleword): Split DWI
> >         and;cmp into andn;cmp $0 as a pre-reload splitter.
> >         (define_expand and<mode>3): Generalize from SWIM1248x to SWIDWI.
> >         (define_insn_and_split "*anddi3_doubleword"): Rename/generalize...
> >         (define_insn_and_split "*and<dwi>3_doubleword"): ... to this.
> >         (define_insn "*andndi3_doubleword"): Rename and generalize...
> >         (define_insn "*andn<mode>3_doubleword): ... to this.
> >         (define_split): Split andn when TARGET_BMI for both <DWI> modes.
> >         (define_split): Split andn when !TARGET_BMI for both <DWI> modes.
> >         (define_expand <any_or><mode>3): Generalize from SWIM1248x to
> > SWIDWI.
> >         (define_insn_and_split "*<any_or><dwi>3_doubleword): Generalize
> >         from DI mode to both <DWI> modes.
> >
> > gcc/testsuite/ChangeLog
> >         * gcc.target/i386/testnot-3.c: New test case.
>
>  (define_expand "and<mode>3"
> -  [(set (match_operand:SWIM1248x 0 "nonimmediate_operand")
> -    (and:SWIM1248x (match_operand:SWIM1248x 1 "nonimmediate_operand")
> -               (match_operand:SWIM1248x 2 "<general_szext_operand>")))]
> +  [(set (match_operand:SWIDWI 0 "nonimmediate_operand")
> +    (and:SWIDWI (match_operand:SWIDWI 1 "nonimmediate_operand")
> +            (match_operand:SWIDWI 2 "<general_operand>")))]

(Didn't notice at yesterday's review)

Please do not change existing predicates, but extend
general_szext_operand mode attribute to handle TImode

-(define_insn_and_split "*anddi3_doubleword"
-  [(set (match_operand:DI 0 "nonimmediate_operand")
-    (and:DI
-     (match_operand:DI 1 "nonimmediate_operand")
-     (match_operand:DI 2 "x86_64_szext_general_operand")))
+(define_insn_and_split "*and<dwi>3_doubleword"
+  [(set (match_operand:<DWI> 0 "nonimmediate_operand")
+    (and:<DWI>
+     (match_operand:<DWI> 1 "nonimmediate_operand")
+     (match_operand:<DWI> 2 "<general_operand>")))

Also here, extended general_szext_operand attribute should handle DI and TImode.

Uros.

      reply	other threads:[~2022-06-07  6:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05 17:19 Roger Sayle
2022-06-05 19:12 ` Uros Bizjak
2022-06-06  8:23   ` Roger Sayle
2022-06-06  9:22     ` Uros Bizjak
2022-06-06 10:25 ` Uros Bizjak
2022-06-06 11:28 ` Uros Bizjak
2022-06-07  6:08   ` 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=CAFULd4aM4f_srcAur6p0gb4zWGd7roR+bK5v7qCeAuwS7RgDzg@mail.gmail.com \
    --to=ubizjak@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --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).