public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Bin Cheng <Bin.Cheng@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>, nd <nd@arm.com>
Subject: Re: [PATCH 01/2]Maintain irreducible region information in vectorizer peeling
Date: Tue, 28 Mar 2017 12:18:00 -0000	[thread overview]
Message-ID: <CAFiYyc3xrOdQsOBSJMkM6Nq0adhLjHViTgGicFEJ0EmF-WQDcg@mail.gmail.com> (raw)
In-Reply-To: <VI1PR0802MB21769C4B77294F7B91499D03E7320@VI1PR0802MB2176.eurprd08.prod.outlook.com>

On Tue, Mar 28, 2017 at 2:01 PM, Bin Cheng <Bin.Cheng@arm.com> wrote:
> Hi,
> This patch fixes a latent bug in vectorizer, specifically, vect_do_peeling doesn't mark newly created edge
> with irreducible flag if the vectorized loop is in irreducible region.  Function checking_verify_loop_structure
> needs to be explicitly called in vectorizer otherwise the issue is covered, but I am okay if we should avoid
> this call.
> Bootstrap and test on x86_64 and AArch64.  This patch causes new failure in gcc.dg/tree-ssa/pr71077.c,
> which uncovers another latent bug in vectorizer.  That will be fixed by next patch.  Is this OK?

Ok (please omit the checking_verify_loop_structure call for now).

Thanks,
Richard.

> 2017-03-27  Bin Cheng  <bin.cheng@arm.com>
>
>         * tree-vect-loop-manip.c (slpeel_add_loop_guard): New param and
>         mark new edge's irreducible flag accordign to it.
>         (vect_do_peeling): Check loop preheader edge's irreducible flag
>         and pass it to function slpeel_add_loop_guard.
>         * tree-vectorizer.c (vectorize_loops): Explicitly call function
>         checking_verify_loop_structure.
>
> gcc/testsuite/ChangeLog
> 2017-03-27  Bin Cheng  <bin.cheng@arm.com>
>
>         * gcc.c-torture/compile/irreducible-loop.c: New.

      reply	other threads:[~2017-03-28 12:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 12:01 Bin Cheng
2017-03-28 12:18 ` 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=CAFiYyc3xrOdQsOBSJMkM6Nq0adhLjHViTgGicFEJ0EmF-WQDcg@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=Bin.Cheng@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nd@arm.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).