From: Richard Biener <richard.guenther@gmail.com>
To: Hongtao Liu <crazylht@gmail.com>
Cc: Liwei Xu <liwei.xu@intel.com>,
wilson@tuliptree.org, hongtao.liu@intel.com,
gcc-patches@gcc.gnu.org, admin@levyhsu.com
Subject: Re: [PATCH] Move scanning pass of forwprop-19.c to dse1 for r13-3212-gb88adba751da63
Date: Mon, 17 Oct 2022 09:07:24 +0200 [thread overview]
Message-ID: <CAFiYyc0qX0hirktb_US=FEufMNojZe0ROVM3699cOw7CzkOPrg@mail.gmail.com> (raw)
In-Reply-To: <CAMZc-bxTQL=L-w3Sx83i6qpQNsx_ZhmGDdQdYqTOdW7WkM1eNA@mail.gmail.com>
On Mon, Oct 17, 2022 at 5:44 AM Hongtao Liu via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> On Mon, Oct 17, 2022 at 11:26 AM Liwei Xu via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
> >
> > gcc/testsuite/ChangeLog:
> >
> > * gcc.dg/tree-ssa/forwprop-19.c: Move scanning pass from forwprop1 to dse1, This fixs
> > the test case fail.
> Looks like an obvious fix to me.
Yes, OK.
Thanks,
Richard.
> > ---
> > gcc/testsuite/gcc.dg/tree-ssa/forwprop-19.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/gcc/testsuite/gcc.dg/tree-ssa/forwprop-19.c b/gcc/testsuite/gcc.dg/tree-ssa/forwprop-19.c
> > index 4d77138b206..6ca81cb6c49 100644
> > --- a/gcc/testsuite/gcc.dg/tree-ssa/forwprop-19.c
> > +++ b/gcc/testsuite/gcc.dg/tree-ssa/forwprop-19.c
> > @@ -1,5 +1,5 @@
> > /* { dg-do compile } */
> > -/* { dg-options "-O -fdump-tree-forwprop1" } */
> > +/* { dg-options "-O -fdump-tree-dse1" } */
> >
> > typedef int vec __attribute__((vector_size (4 * sizeof (int))));
> > void f (vec *x1, vec *x2)
> > @@ -11,4 +11,4 @@ void f (vec *x1, vec *x2)
> > *x1 = z;
> > }
> >
> > -/* { dg-final { scan-tree-dump-not "VEC_PERM_EXPR" "forwprop1" } } */
> > +/* { dg-final { scan-tree-dump-not "VEC_PERM_EXPR" "dse1" } } */
> > --
> > 2.18.2
> >
>
>
> --
> BR,
> Hongtao
prev parent reply other threads:[~2022-10-17 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 3:24 Liwei Xu
2022-10-17 3:43 ` Hongtao Liu
2022-10-17 7:07 ` Richard Biener [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='CAFiYyc0qX0hirktb_US=FEufMNojZe0ROVM3699cOw7CzkOPrg@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=admin@levyhsu.com \
--cc=crazylht@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hongtao.liu@intel.com \
--cc=liwei.xu@intel.com \
--cc=wilson@tuliptree.org \
/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).