From: Richard Biener <richard.guenther@gmail.com>
To: Marc Glisse <marc.glisse@inria.fr>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: VEC_COND_EXPR optimizations
Date: Fri, 31 Jul 2020 14:08:20 +0200 [thread overview]
Message-ID: <CAFiYyc2ZTndfja3bteyqokxnNNC8_JcMyagCWb6eBXdgcR2mtQ@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc08soPXchoHnz6AbMboYg-9wiXxVb2bW0O0Pq29qUqQDQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 6377 bytes --]
On Fri, Jul 31, 2020 at 1:47 PM Richard Biener
<richard.guenther@gmail.com> wrote:
>
> On Fri, Jul 31, 2020 at 1:39 PM Richard Biener
> <richard.guenther@gmail.com> wrote:
> >
> > On Fri, Jul 31, 2020 at 1:35 PM Richard Biener
> > <richard.guenther@gmail.com> wrote:
> > >
> > > On Thu, Jul 30, 2020 at 9:49 AM Marc Glisse <marc.glisse@inria.fr> wrote:
> > > >
> > > > When vector comparisons were forced to use vec_cond_expr, we lost a number
> > > > of optimizations (my fault for not adding enough testcases to prevent
> > > > that). This patch tries to unwrap vec_cond_expr a bit so some
> > > > optimizations can still happen.
> > > >
> > > > I wasn't planning to add all those transformations together, but adding
> > > > one caused a regression, whose fix introduced a second regression, etc.
> > > >
> > > > Using a simple fold_binary internally looks like an ok compromise to me.
> > > > It remains cheap enough (not recursive, and vector instructions are not
> > > > that frequent), while still allowing more than const_binop (X|0 or X&X for
> > > > instance). The transformations are quite conservative with :s and folding
> > > > only if everything simplifies, we may want to relax this later. And of
> > > > course we are going to miss things like a?b:c + a?c:b -> b+c.
> > > >
> > > > In terms of number of operations, some transformations turning 2
> > > > VEC_COND_EXPR into VEC_COND_EXPR + BIT_IOR_EXPR + BIT_NOT_EXPR might not
> > > > look like a gain... I expect the bit_not disappears in most cases, and
> > > > VEC_COND_EXPR looks more costly than a simpler BIT_IOR_EXPR.
> > > >
> > > > I am a bit confused that with avx512 we get types like "vector(4)
> > > > <signed-boolean:2>" with :2 and not :1 (is it a hack so true is 1 and not
> > > > -1?), but that doesn't matter for this patch.
> > > >
> > > > Regtest+bootstrap on x86_64-pc-linux-gnu
> > >
> > > + (with
> > > + {
> > > + tree rhs1, rhs2 = NULL;
> > > + rhs1 = fold_binary (op, type, @1, @3);
> > > + if (rhs1 && is_gimple_val (rhs1))
> > > + rhs2 = fold_binary (op, type, @2, @3);
> > >
> > > ICK. I guess a more match-and-simplify way would be
> > >
> > > (with
> > > {
> > > tree rhs1, rhs2;
> > > gimple_match_op op (gimple_match_cond::UNCOND, op,
> > > type, @1, @3);
> > > if (op.resimplify (NULL, valueize)
> > > && gimple_simplified_result_is_gimple_val (op))
> > > {
> > > rhs1 = op.ops[0];
> > > ... other operand ...
> > > }
> > >
> > > now in theory we could invent some new syntax for this, like
> > >
> > > (simplify
> > > (op (vec_cond:s @0 @1 @2) @3)
> > > (vec_cond @0 (op:x @1 @3) (op:x @2 @3)))
> > >
> > > and pick something better instead of :x (:s is taken,
> > > would be 'simplified', :c is taken would be 'constexpr', ...).
> > >
> > > _Maybe_ just
> > >
> > > (simplify
> > > (op (vec_cond:s @0 @1 @2) @3)
> > > (vec_cond:x @0 (op @1 @3) (op @2 @3)))
> > >
> > > which would have the same practical meaning as passing
> > > NULL for the seq argument to simplification - do not allow
> > > any intermediate stmt to be generated.
> >
> > Note I specifically do not like those if (it-simplifies) checks
> > because we already would code-generate those anyway. For
> >
> > (simplify
> > (plus (vec_cond:s @0 @1 @2) @3)
> > (vec_cond @0 (plus @1 @3) (plus @2 @3)))
> >
> > we get
> >
> > res_op->set_op (VEC_COND_EXPR, type, 3);
> > res_op->ops[0] = captures[1];
> > res_op->ops[0] = unshare_expr (res_op->ops[0]);
> > {
> > tree _o1[2], _r1;
> > _o1[0] = captures[2];
> > _o1[1] = captures[4];
> > gimple_match_op tem_op (res_op->cond.any_else
> > (), PLUS_EXPR, TREE_TYPE (_o1[0]), _o1[0], _o1[1]);
> > tem_op.resimplify (lseq, valueize);
> > _r1 = maybe_push_res_to_seq (&tem_op, lseq); (****)
> > if (!_r1) return false;
> > res_op->ops[1] = _r1;
> > }
> > {
> > tree _o1[2], _r1;
> > _o1[0] = captures[3];
> > _o1[1] = captures[4];
> > gimple_match_op tem_op (res_op->cond.any_else
> > (), PLUS_EXPR, TREE_TYPE (_o1[0]), _o1[0], _o1[1]);
> > tem_op.resimplify (lseq, valueize);
> > _r1 = maybe_push_res_to_seq (&tem_op, lseq); (***)
> > if (!_r1) return false;
> > res_op->ops[2] = _r1;
> > }
> > res_op->resimplify (lseq, valueize);
> > return true;
> >
> > and the only change required would be to pass NULL to maybe_push_res_to_seq
> > here instead of lseq at the (***) marked points.
>
> (simplify
> (plus (vec_cond:s @0 @1 @2) @3)
> (vec_cond:l @0 (plus @1 @3) (plus @2 @3)))
>
> 'l' for 'force leaf'. I'll see if I can quickly cme up with a patch.
The attached prototype works for
(simplify
(plus (vec_cond:s @0 @1 @2) @3)
(vec_cond @0 (plus:l @1 @3) (plus:l @2 @3)))
but ':...' is already taken for an explicitly specified type so I have
to think about sth better. As you see I've also moved it to
the actual ops that should simplify. It doesn't work on the
outermost expression but I guess it doesn't make sense there
(adding support would be possible).
Now I need some non-ambiguous syntax... it currently
is id[:type][@cid] so maybe id[!][:type][@cid]. I guess
non-ambiguous is good enough?
Richard.
> Richard.
>
>
>
> > Richard.
> >
> > > The other "simple" patterns look good, you can commit
> > > them separately if you like.
> > >
> > > Richard.
> > >
> > > > 2020-07-30 Marc Glisse <marc.glisse@inria.fr>
> > > >
> > > > PR tree-optimization/95906
> > > > PR target/70314
> > > > * match.pd ((c ? a : b) op d, (c ? a : b) op (c ? d : e),
> > > > (v ? w : 0) ? a : b, c1 ? c2 ? a : b : b): New transformations.
> > > >
> > > > * gcc.dg/tree-ssa/andnot-2.c: New file.
> > > > * gcc.dg/tree-ssa/pr95906.c: Likewise.
> > > > * gcc.target/i386/pr70314.c: Likewise.
> > > >
> > > > --
> > > > Marc Glisse
[-- Attachment #2: p --]
[-- Type: application/octet-stream, Size: 2219 bytes --]
diff --git a/gcc/genmatch.c b/gcc/genmatch.c
index 0a8cba62e0c..9a34fe71e78 100644
--- a/gcc/genmatch.c
+++ b/gcc/genmatch.c
@@ -697,12 +697,13 @@ public:
expr (id_base *operation_, location_t loc, bool is_commutative_ = false)
: operand (OP_EXPR, loc), operation (operation_),
ops (vNULL), expr_type (NULL), is_commutative (is_commutative_),
- is_generic (false), force_single_use (false), opt_grp (0) {}
+ is_generic (false), force_single_use (false), force_leaf (false),
+ opt_grp (0) {}
expr (expr *e)
: operand (OP_EXPR, e->location), operation (e->operation),
ops (vNULL), expr_type (e->expr_type), is_commutative (e->is_commutative),
is_generic (e->is_generic), force_single_use (e->force_single_use),
- opt_grp (e->opt_grp) {}
+ force_leaf (e->force_leaf), opt_grp (e->opt_grp) {}
void append_op (operand *op) { ops.safe_push (op); }
/* The operator and its operands. */
id_base *operation;
@@ -717,6 +718,9 @@ public:
/* Whether pushing any stmt to the sequence should be conditional
on this expression having a single-use. */
bool force_single_use;
+ /* Whether in the result expression this should be a leaf node
+ with any children simplified down to simple operands. */
+ bool force_leaf;
/* If non-zero, the group for optional handling. */
unsigned char opt_grp;
virtual void gen_transform (FILE *f, int, const char *, bool, int,
@@ -2520,7 +2524,8 @@ expr::gen_transform (FILE *f, int indent, const char *dest, bool gimple,
fprintf (f, ");\n");
fprintf_indent (f, indent, "tem_op.resimplify (lseq, valueize);\n");
fprintf_indent (f, indent,
- "_r%d = maybe_push_res_to_seq (&tem_op, lseq);\n", depth);
+ "_r%d = maybe_push_res_to_seq (&tem_op, %s);\n", depth,
+ !force_leaf ? "lseq" : "NULL");
fprintf_indent (f, indent,
"if (!_r%d) return false;\n",
depth);
@@ -4250,7 +4255,12 @@ parser::parse_expr ()
{
const char *s = get_ident ();
if (!parsing_match_operand)
- expr_type = s;
+ {
+ if (*s == 'l')
+ e->force_leaf = true;
+ else
+ expr_type = s;
+ }
else
{
const char *sp = s;
next prev parent reply other threads:[~2020-07-31 12:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 7:49 Marc Glisse
2020-07-31 11:18 ` Richard Sandiford
2020-07-31 11:38 ` Marc Glisse
2020-07-31 11:43 ` Richard Biener
2020-07-31 11:57 ` Marc Glisse
2020-07-31 12:50 ` Richard Sandiford
2020-07-31 12:59 ` Richard Biener
2020-07-31 13:01 ` Marc Glisse
2020-07-31 13:13 ` Marc Glisse
2020-07-31 11:35 ` Richard Biener
2020-07-31 11:39 ` Richard Biener
2020-07-31 11:47 ` Richard Biener
2020-07-31 12:08 ` Richard Biener [this message]
2020-07-31 12:12 ` Marc Glisse
2020-08-05 13:32 ` VEC_COND_EXPR optimizations v2 Marc Glisse
2020-08-05 14:24 ` Richard Biener
2020-08-06 8:17 ` Christophe Lyon
2020-08-06 9:05 ` Marc Glisse
2020-08-06 11:25 ` Christophe Lyon
2020-08-06 11:42 ` Marc Glisse
2020-08-06 12:00 ` Christophe Lyon
2020-08-06 18:07 ` Marc Glisse
2020-08-07 6:38 ` Richard Biener
2020-08-07 8:33 ` Marc Glisse
2020-08-07 8:47 ` Richard Biener
2020-08-07 12:15 ` Marc Glisse
2020-08-07 13:04 ` Richard Biener
2020-08-06 10:29 ` Richard Biener
2020-08-06 11:11 ` Marc Glisse
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=CAFiYyc2ZTndfja3bteyqokxnNNC8_JcMyagCWb6eBXdgcR2mtQ@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=marc.glisse@inria.fr \
/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).