public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dpatel at apple dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/18441] Vectorizer: add a command line for simple vectorizer report Date: Mon, 13 Dec 2004 20:16:00 -0000 [thread overview] Message-ID: <20041213201615.4405.qmail@sourceware.org> (raw) In-Reply-To: <20041112021622.18441.giovannibajo@libero.it> ------- Additional Comments From dpatel at apple dot com 2004-12-13 20:16 ------- Try -fdump-tree-vect-stats. It produces more user friendly output compared to -details. I am not fan of putting such diagnostics as part of warnings/info/errors. IMO, we should enhance/ update -fdump-tree-vect-stats to meet user's requirements. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18441
next prev parent reply other threads:[~2004-12-13 20:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-11-12 2:16 [Bug tree-optimization/18441] New: " giovannibajo at libero dot it 2004-11-12 2:45 ` [Bug tree-optimization/18441] " pinskia at gcc dot gnu dot org 2004-12-13 20:16 ` dpatel at apple dot com [this message] 2004-12-22 19:00 ` leehod at il dot ibm dot com 2005-01-19 19:28 ` leehod at il dot ibm dot com 2005-02-10 0:13 ` dorit at il dot ibm dot com 2005-05-21 12:51 ` pinskia at gcc dot gnu dot 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=20041213201615.4405.qmail@sourceware.org \ --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).