public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bin Cheng <Bin.Cheng@arm.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: nd <nd@arm.com>
Subject: [PATCH GCC][OBVIOUS]Fix dump info by reporting malformed loop nest.
Date: Wed, 16 Mar 2016 09:28:00 -0000	[thread overview]
Message-ID: <AM4PR08MB1140F0EF6A0708536973D10EE78A0@AM4PR08MB1140.eurprd08.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 484 bytes --]

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?

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.

[-- Attachment #2: dump-msg-for-malformed-loop-nest-20160308.txt --]
[-- Type: text/plain, Size: 606 bytes --]

Index: gcc/tree-vect-loop.c
===================================================================
--- gcc/tree-vect-loop.c	(revision 234057)
+++ gcc/tree-vect-loop.c	(working copy)
@@ -1772,8 +1772,9 @@ vect_analyze_loop_2 (loop_vec_info loop_vinfo, boo
     {
       if (dump_enabled_p ())
 	dump_printf_loc (MSG_MISSED_OPTIMIZATION, vect_location,
-			 "not vectorized: loop contains function calls"
-			 " or data references that cannot be analyzed\n");
+			 "not vectorized: loop nest containing two "
+			 "or more consecutive inner loops cannot be "
+			 "vectorized\n");
       return false;
     }
 

             reply	other threads:[~2016-03-16  9:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16  9:28 Bin Cheng [this message]
2016-03-16  9:45 ` 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=AM4PR08MB1140F0EF6A0708536973D10EE78A0@AM4PR08MB1140.eurprd08.prod.outlook.com \
    --to=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).