public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@acm.org>
To: Jakub Jelinek <jakub@redhat.com>, Alexander Monakov <amonakov@ispras.ru>
Cc: Richard Biener <richard.guenther@gmail.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Kill -fdump-translation-unit
Date: Wed, 10 May 2017 21:59:00 -0000	[thread overview]
Message-ID: <1fdd4c0e-06b1-1c9d-cd83-f31af9ee27df@acm.org> (raw)
In-Reply-To: <20170510175826.GH1809@tucnak>

On 05/10/2017 01:58 PM, Jakub Jelinek wrote:

>> 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.

Prior to Alex mentioning it, I was unaware of such parsers -- I'm 
surprised.  This is not a data interchange format, it's a debugging dump.

The fellow on IRC failed to mention that, and made the claim that the TU 
dump was the simplest way of determining sizeof (time_t) when one has a 
cross compiler.

nathan

-- 
Nathan Sidwell

  parent reply	other threads:[~2017-05-10 21:18 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
2017-05-10 21:59       ` Nathan Sidwell [this message]
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=1fdd4c0e-06b1-1c9d-cd83-f31af9ee27df@acm.org \
    --to=nathan@acm.org \
    --cc=amonakov@ispras.ru \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --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).