public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "singhai at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/58134] [4.8/4.9 Regression] -ftree-vectorizer-verbose=<n> shows vectroiyed loops only for N== 1 and N >2 but not for N==2 Date: Mon, 12 Aug 2013 19:13:00 -0000 [thread overview] Message-ID: <bug-58134-4-fkoRSI2CRH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58134-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58134 --- Comment #3 from Sharad Singhai <singhai at gcc dot gnu.org> --- I think this is the intended behavior. While working on the new dump infrastructure, I modified the behavior of -ftree-vectorizer-verbose. Thus right now -ftree-vectorizer-verbose=1 : dump info about optimized loops ...=2 : dump info about missed loops ...>2 : dump info about optimized _and_ missed loops Thus at 3 and greater, you are again seeing info available at 1. But really, only 1 and 2 are meaningful. Anything higher is a combination of these two kinds of information. This was a way to preserve compatibility with old scripts, while deprecating this flag. I didn't see any tests relying on the old behavior. Here is the current documentation about this flag in gcc.info: `-ftree-vectorizer-verbose=N' This option is deprecated and is implemented in terms of `-fopt-info'. Please use `-fopt-info-KIND' form instead, where KIND is one of the valid opt-info options. It prints additional optimization information. For N=0 no diagnostic information is reported. If N=1 the vectorizer reports each loop that got vectorized, and the total number of loops that got vectorized. If N=2 the vectorizer reports locations which could not be vectorized and the reasons for those. For any higher verbosity levels all the analysis and transformation information from the vectorizer is reported.
next prev parent reply other threads:[~2013-08-12 19:13 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-12 6:04 [Bug middle-end/58134] New: " burnus at gcc dot gnu.org 2013-08-12 18:00 ` [Bug middle-end/58134] " burnus at gcc dot gnu.org 2013-08-12 18:05 ` [Bug middle-end/58134] [4.8/4.9 Regression] " burnus at gcc dot gnu.org 2013-08-12 19:13 ` singhai at gcc dot gnu.org [this message] 2013-08-28 9:21 ` [Bug middle-end/58134] [4.8/4.9 Regression] -ftree-vectorizer-verbose=<n> shows vectorized " rguenth at gcc dot gnu.org 2013-08-29 1:05 ` singhai at gcc dot gnu.org 2013-10-16 9:49 ` jakub at gcc dot gnu.org 2013-10-31 16:11 ` singhai at gcc dot gnu.org
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=bug-58134-4-fkoRSI2CRH@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).