From: Jakub Jelinek <jakub@redhat.com>
To: Alexander Monakov <amonakov@ispras.ru>
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 17:59:00 -0000 [thread overview]
Message-ID: <20170510175826.GH1809@tucnak> (raw)
In-Reply-To: <alpine.LNX.2.20.13.1705102033250.11444@monopod.intra.ispras.ru>
On Wed, May 10, 2017 at 08:51:22PM +0300, Alexander Monakov wrote:
> On Wed, 10 May 2017, Richard Biener wrote:
>
> > On Tue, May 9, 2017 at 5:41 PM, Nathan Sidwell <nathan@acm.org> wrote:
> > > -fdump-translation-unit is an inscrutably opaque dump. It turned out that
> > > most of the uses of the tree-dump header file was to indirectly get at
> > > dumpfile.h, and the dump_function entry point it had forwarded to a dumper
> > > in tree-cfg.c. The gimple dumper would use its node dumper when asked for a
> > > raw dump, but that was about it.
> > >
> > > We have prettier printers now. This patch nukes the tu dumper. ok?
> >
> > Ok if nobody objects within 24 hours.
>
> There was a reasonable IMO objection on the IRC (sadly, I can't say the same
> about the responses that person received from Nathan).
>
> A quick search indicates that people have published .tu parsers in Perl, JS
> (producing json), the person objecting on IRC apparently used Python, and I'm
> aware of another Python-based parser by Bruce Merry.
>
> My takeaway from this is that people cared enough about this to build and
> publish parsers in their language of choice, and that apparently it is or was
> feature-rich enough for them to use. Despite the format being undocumented and
> formally not supported.
>
> The motivation put forward in the opening mail ("is an inscutably opaque dump")
> seems like a weak reason for removal.
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. 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?
Jakub
next prev parent reply other threads:[~2017-05-10 17:58 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 [this message]
2017-05-10 20:57 ` Alexander Monakov
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=20170510175826.GH1809@tucnak \
--to=jakub@redhat.com \
--cc=amonakov@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--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).