From: Ian Lance Taylor <iant@google.com>
To: Xin Tong <xerox.time.tech@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: print gcc optimization log
Date: Thu, 16 Aug 2012 11:36:00 -0000 [thread overview]
Message-ID: <CAKOQZ8wDnjE5Rnj8q0EK-WtrzSKjutua36dKqxsVBgWXfoJOSg@mail.gmail.com> (raw)
In-Reply-To: <CALKntY3qe_=7VCw_yb+ixZPbaZRT1fOgO1p8VNE2y8W_eks2eg@mail.gmail.com>
On Wed, Aug 15, 2012 at 8:58 PM, Xin Tong <xerox.time.tech@gmail.com> wrote:
> I sometimes run into issues where i want to figure out why gcc is
> performing a specific optimization and what the optimization affects
> the tree. is there any documents on how to print gcc optimizations and
> code generation logs ?
Unfortunately GCC has very little in the way of logs intended for end
users. About all I know is the -ftree-vectorizer-verbose information,
which gives useful feedback about the vectorization optimizations.
You can a lot of information by using -fdump-tree-all-details
-fdump-rtl-all-details, but it's difficult to interpret without the
source code and a working knowledge of GCC internals.
Ian
next prev parent reply other threads:[~2012-08-16 5:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 10:58 Xin Tong
2012-08-16 11:36 ` Ian Lance Taylor [this message]
2012-08-16 15:37 ` Xin Tong
2012-08-16 18:31 ` Ian Lance Taylor
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=CAKOQZ8wDnjE5Rnj8q0EK-WtrzSKjutua36dKqxsVBgWXfoJOSg@mail.gmail.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=xerox.time.tech@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).