From: Pierre Vittet <piervit@pvittet.com>
To: gcc@gcc.gnu.org
Subject: Re: role of dump_file notably for/in plugins?
Date: Thu, 01 Sep 2011 15:18:00 -0000 [thread overview]
Message-ID: <4E5FA24E.5030205@pvittet.com> (raw)
In-Reply-To: <20110831142447.GD26845@ours.starynkevitch.net>
Hello,
From what I understand, the question is not really how do we dump passes
but what a pass (from a plugin or not) should dump? So the question is
what do you expect from a dump file?
Do you expect to have the full internal representation of the code after
the end of the pass? For many dump files, we just get this (lower,cfg,
ssa...).
Or do you expect something more oriented on what the pass did? Like
"this pass remove three unreable basicblocks, they were located here,
here and here"?
Maybe there is no particular rules and it just depends of the pass.
However I guess there should some clear rules about this. Dump files can
be quite useful to understand the compiler behavior (sometimes it is a
huge task to search using the debugger).
Thanks.
Pierre Vittet
prev parent reply other threads:[~2011-09-01 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 14:25 Basile Starynkevitch
2011-08-31 14:28 ` Richard Guenther
2011-08-31 14:47 ` David Malcolm
2011-09-01 15:18 ` Pierre Vittet [this message]
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=4E5FA24E.5030205@pvittet.com \
--to=piervit@pvittet.com \
--cc=gcc@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: 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).