public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hongtao Liu <crazylht@gmail.com>
To: Liwei Xu <liwei.xu@intel.com>
Cc: gcc-patches@gcc.gnu.org, hongtao.liu@intel.com,
	wilson@tuliptree.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 11:43:23 +0800	[thread overview]
Message-ID: <CAMZc-bxTQL=L-w3Sx83i6qpQNsx_ZhmGDdQdYqTOdW7WkM1eNA@mail.gmail.com> (raw)
In-Reply-To: <20221017032429.282693-1-liwei.xu@intel.com>

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.
> ---
>  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

  reply	other threads:[~2022-10-17  3:43 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 [this message]
2022-10-17  7:07   ` Richard Biener

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='CAMZc-bxTQL=L-w3Sx83i6qpQNsx_ZhmGDdQdYqTOdW7WkM1eNA@mail.gmail.com' \
    --to=crazylht@gmail.com \
    --cc=admin@levyhsu.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).