From: Alexander Monakov <amonakov@ispras.ru>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
Nathan Sidwell <nathan@acm.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Kill -fdump-translation-unit
Date: Wed, 10 May 2017 20:57:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.20.13.1705102341130.11444@monopod.intra.ispras.ru> (raw)
In-Reply-To: <20170510175826.GH1809@tucnak>
On Wed, 10 May 2017, Jakub Jelinek wrote:
> Can it at least be taken out of -fdump-tree-all? It is huge, often larger
> than the sum of all the other dump files, and don't remember ever using it
> for anything.
Yes, apart from advertising the capability I don't imagine it's useful to
produce that dump without a special flag.
> Instead of trying to write a parser for it and reconstructing
> something you can then later analyze, isn't it better to just write a plugin
> that can analyze it directly?
I think I can understand people writing a parser when it's sufficient; it won't
need to be recompiled for a specific compiler version (with headers from that
compiler), won't crash the compiler if you did something wrong. For people more
familiar with a dynamic language like Python than C/C++ it may be just more
comfortable to do it that way.
Alexander
next prev parent reply other threads:[~2017-05-10 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 15:46 Nathan Sidwell
2017-05-10 8:58 ` Richard Biener
2017-05-10 17:51 ` Alexander Monakov
2017-05-10 17:59 ` Jakub Jelinek
2017-05-10 20:57 ` Alexander Monakov [this message]
2017-05-10 21:59 ` Nathan Sidwell
2017-05-11 15:52 ` Nathan Sidwell
2017-05-11 17:37 ` Rainer Orth
2017-05-11 17:48 ` Nathan Sidwell
2017-05-11 17:50 ` Rainer Orth
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=alpine.LNX.2.20.13.1705102341130.11444@monopod.intra.ispras.ru \
--to=amonakov@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=nathan@acm.org \
--cc=richard.guenther@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).