From: Uros Bizjak <ubizjak@gmail.com>
To: Toon Moene <toon@moene.indiv.nluug.nl>
Cc: GCC <gcc@gcc.gnu.org>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: HIRLAM with -ftree-loop-distribution.
Date: Sun, 16 Dec 2007 12:44:00 -0000 [thread overview]
Message-ID: <47651A7C.4090009@gmail.com> (raw)
Hello!
> There something weird going on with the count of the "loops not
> vectorized" - every successfully vectorized loop gets an additional
> message:
>
> note: not vectorized: vectorization may not beprofitable.
This is due to switching on vector cost model by default for x86.
BTW: Attached patch fixed the message by adding the space between "be"
and "profitable.". Patch was commited to SVN after bootstrappnig on x86_64.
2007-12-16 Uros Bizjak <ubizjak@gmail.com>
* tree-vect-transform.c (conservative_cost_threshold): Add missing
space to "not vectorized" message.
Uros.
Index: tree-vect-transform.c
===================================================================
--- tree-vect-transform.c (revision 130987)
+++ tree-vect-transform.c (working copy)
@@ -6552,7 +6552,7 @@
th = (unsigned) min_profitable_iters;
if (vect_print_dump_info (REPORT_UNVECTORIZED_LOOPS))
- fprintf (vect_dump, "not vectorized: vectorization may not be"
+ fprintf (vect_dump, "not vectorized: vectorization may not be "
"profitable.");
if (th && vect_print_dump_info (REPORT_DETAILS))
next reply other threads:[~2007-12-16 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 12:44 Uros Bizjak [this message]
2007-12-16 13:34 ` Toon Moene
2007-12-16 14:14 ` Dorit Nuzman
2007-12-16 14:54 ` Dorit Nuzman
-- strict thread matches above, loose matches on Subject: below --
2007-12-16 12:31 Toon Moene
2007-12-16 17:53 ` Sebastian Pop
2007-12-16 19:43 ` Toon Moene
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=47651A7C.4090009@gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=toon@moene.indiv.nluug.nl \
/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).