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 GCC][OBVIOUS]Fix dump info by reporting malformed loop nest.
Date: Wed, 16 Mar 2016 09:45:00 -0000 [thread overview]
Message-ID: <CAFiYyc0NYDAyfw7yWWZ=TnjW+zZ68r7uMYw+eN34sD21JWtZpg@mail.gmail.com> (raw)
In-Reply-To: <AM4PR08MB1140F0EF6A0708536973D10EE78A0@AM4PR08MB1140.eurprd08.prod.outlook.com>
On Wed, Mar 16, 2016 at 10:28 AM, Bin Cheng <Bin.Cheng@arm.com> wrote:
> Hi,
> This is an obvious change to dump message in vect_analyze_loop_2. Apparently, the wrong message is copies/pasted from another place, the code has nothing to do with function calls or data references. We should report that loop cannot be vectorized because of malformed loop nest.
> Build successfully. Is it OK?
Ok.
Richard.
> Thanks,
> bin
>
> 2016-03-16 Bin Cheng <bin.cheng@arm.com>
>
> * tree-vect-loop.c (vect_analyze_loop_2): Fix wrong dump info by
> reporting malformed loop nest.
prev parent reply other threads:[~2016-03-16 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 9:28 Bin Cheng
2016-03-16 9:45 ` 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='CAFiYyc0NYDAyfw7yWWZ=TnjW+zZ68r7uMYw+eN34sD21JWtZpg@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).