public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dorit Nuzman <DORIT@il.ibm.com>
To: Toon Moene <toon@moene.indiv.nluug.nl>
Cc: GCC <gcc@gcc.gnu.org>, Uros Bizjak <ubizjak@gmail.com>
Subject: Re: HIRLAM with -ftree-loop-distribution.
Date: Sun, 16 Dec 2007 14:14:00 -0000	[thread overview]
Message-ID: <OF63685358.814443EB-ONC22573B3.004C96E0-C22573B3.004D197E@il.ibm.com> (raw)
In-Reply-To: <4765225A.1030803@moene.indiv.nluug.nl>

> Uros Bizjak wrote:
>
> >> note: not vectorized: vectorization may not beprofitable.
> >
> > This is due to switching on vector cost model by default for x86.
>
> Ah, but my hidden critique of the message was:
> -ftree-vectorizer-verbose=2 should *only* tell us:
>
> 1. Which loops are vectorized.
> 2. Which are not - and why (in a single sentence).
>
> For more detailed logging, one should use -ftree-vectorizer-verbose=n
> with n>2, IMNSHO.
>

yes, you are right. this printing should be either removed (as it's anyhow
already being printed also under REPORT_DETAILS), or we may want to add a
new verbosity level (lower than REPORT_DETAILS) for cost-model info
("REPORT_COST").

dorit

> Kind regards,
>
> --
> Toon Moene - e-mail: toon@moene.indiv.nluug.nl - phone: +31 346 214290
> Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
> At home: http://moene.indiv.nluug.nl/~toon/
> GNU Fortran's path to Fortran 2003: http://gcc.gnu.org/wiki/Fortran2003

  reply	other threads:[~2007-12-16 13:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-16 12:44 Uros Bizjak
2007-12-16 13:34 ` Toon Moene
2007-12-16 14:14   ` Dorit Nuzman [this message]
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=OF63685358.814443EB-ONC22573B3.004C96E0-C22573B3.004D197E@il.ibm.com \
    --to=dorit@il.ibm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=toon@moene.indiv.nluug.nl \
    --cc=ubizjak@gmail.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).