From: Uros Bizjak <ubizjak@gmail.com>
To: Roger Sayle <roger@nextmovesoftware.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [x86 PATCH take #2] Doubleword version of and; cmp to not; test optimization.
Date: Tue, 5 Jul 2022 10:24:37 +0200 [thread overview]
Message-ID: <CAFULd4bgSxpqG9zzV5sc=Fe04JAkC3Gs1sVxJFFJBB0F+s8q3Q@mail.gmail.com> (raw)
In-Reply-To: <CAFULd4bKEYTVpGU6tOz5BdnDL1d2Qj+Tm+SN-uWQvd8DOm5rOw@mail.gmail.com>
On Tue, Jul 5, 2022 at 9:56 AM Uros Bizjak <ubizjak@gmail.com> wrote:
>
> On Mon, Jul 4, 2022 at 9:11 PM Roger Sayle <roger@nextmovesoftware.com> wrote:
> >
> >
> > This patch is the latest revision of the patch originally posted at:
> > https://gcc.gnu.org/pipermail/gcc-patches/2022-June/596201.html
> >
> > This patch extends the earlier 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 from 15 instructions:
> >
> > movq %rdi, %r8
> > movq %rsi, %rax
> > movq %rax, %rdi
> > movq %r8, %rsi
> > movq %rdx, %r8
> > andq %rdx, %rsi
> > andq %rcx, %rdi
> > movq %rsi, %rax
> > movq %rdi, %rdx
> > xorq %r8, %rax
> > xorq %rcx, %rdx
> > orq %rdx, %rax
> > sete %al
> > movzbl %al, %eax
> > ret
> >
> > to the slightly better 13 instructions:
> >
> > movq %rdi, %r8
> > movq %rsi, %rax
> > movq %r8, %rsi
> > movq %rax, %rdi
> > notq %rsi
> > notq %rdi
> > andq %rdx, %rsi
> > andq %rcx, %rdi
> > movq %rsi, %rax
> > orq %rdi, %rax
> > sete %al
> > movzbl %al, %eax
> > ret
> >
> > Now that all of the doubleword pieces are already in the tree, this
> > patch is now much shorter (an rtx_costs improvement and a single new
> > define_insn_and_split), however I couldn't resist including two very
> > minor pattern naming tweaks/clean-ups to fix nits.
> >
> > This revised 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, and on --target_board=unix{-m32} with a single new
> > failure; the other dg-final in gcc.target/i386/pr65105-5.c now also
> > fails (as that code diverges further from the expected vectorized
> > output). This is progress as both FAILs in pr65105-5.c may now be
> > fixed by changes localized to the STV pass. OK for mainline?
> >
> >
> > 2022-07-04 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.
> > (*andn<dwi>3_doubleword_bmi): Use <dwi> instead of <mode> in name.
> > (*<any_or><dwi>3_doubleword): Likewise.
> >
> > gcc/testsuite/ChangeLog
> > * gcc.target/i386/testnot-3.c: New test case.
> >
>
>
> +;; Split and;cmp (as optimized by combine) into andn;cmp $0
> +(define_insn_and_split "*test<mode>_not_doubleword"
> + [(set (reg:CCZ FLAGS_REG)
> + (compare:CCZ
> + (and:DWI
> + (not:DWI (match_operand:DWI 0 "nonimmediate_operand"))
> + (match_operand:DWI 1 "nonimmediate_operand"))
> + (const_int 0)))]
> + "ix86_pre_reload_split ()"
> + "#"
> + "&& 1"
> + [(parallel
> + [(set (match_dup 2) (and:DWI (not:DWI (match_dup 0)) (match_dup 1)))
> + (clobber (reg:CC FLAGS_REG))])
> + (set (reg:CCZ FLAGS_REG) (compare:CCZ (match_dup 2) (const_int 0)))]
> {
> + operands[0] = force_reg (<MODE>mode, operands[0]);
> operands[2] = gen_reg_rtx (<MODE>mode);
> })
>
> I don't think we can count on a follow-up split to lower ANDN for
> !TARGET_BMI case, it is also a pre-reload splitter.
Actually, splitters *CAN* be chained:
Splitting with gen_split_231 (i386.md:10408)
scanning new insn with uid = 30.
scanning new insn with uid = 31.
deleting insn with uid = 12.
Splitting with gen_split_235 (i386.md:10444)
scanning new insn with uid = 32.
scanning new insn with uid = 33.
deleting insn with uid = 30.
Splitting with gen_split_2 (i386.md:1510)
scanning new insn with uid = 34.
scanning new insn with uid = 35.
scanning new insn with uid = 36.
scanning new insn with uid = 37.
deleting insn with uid = 31.
deleting insn with uid = 12.
INSNs are recognized after they are split.
The patch is OK as is.
Thanks,
Uros.
prev parent reply other threads:[~2022-07-05 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 19:11 Roger Sayle
2022-07-05 7:56 ` Uros Bizjak
2022-07-05 8:24 ` 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='CAFULd4bgSxpqG9zzV5sc=Fe04JAkC3Gs1sVxJFFJBB0F+s8q3Q@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).