From: Diego Novillo <dnovillo@google.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: Richard Guenther <rguenther@suse.de>,
gcc@gnu.org, Jan Hubicka <jh@suse.cz>,
Lawrence Crowl <crowl@google.com>
Subject: Re: [pph] Adapting LTO streaming for front end AST saving
Date: Wed, 23 Mar 2011 16:49:00 -0000 [thread overview]
Message-ID: <AANLkTikbCEPbRuoaY8gYrzDputetd3A8VgA+yigrXpUc@mail.gmail.com> (raw)
In-Reply-To: <20110323163858.GA13705@atrey.karlin.mff.cuni.cz>
On Wed, Mar 23, 2011 at 12:38, Jan Hubicka <hubicka@ucw.cz> wrote:
>> think it would be much easier if you worked with a copy (ugh,
>> streaming trees again....).
>
> I also think using same machinery for FE/gimple is a mistake. Trees are making
> life hard since they are interface in between FE<->gimplifier, part of gimple,
> interface for RTL expansion and way we represent debug info.
Yes, but this is only part of the common machinery. I'm actually more
interested in the other functionality. Keeping string tables, symbol
tables, file sections, ability to stream shared pointers by creating
references, etc.
As gimple gets rid of trees, we can transition that code into the
front end. The common code that remains, we can add hooks so each
user implements its own functionality.
> Those are not neccesarily related things and tying them together makes
> things harder to optimize & cleanup.
No, that's not the intent. I simply want to re-use common code. We
will have streamers for debug info, and passes have their own
streamers. PPH is adding another streamer in the front end. All I'm
looking for is to have a set of common streaming code I can use.
> I would rather see well define Gimple bitcode rather than designing common
> format to handle PCHs, LTO and external templates on the top of existing trees.
In as much as gimple is still using tree codes, those would remain in
common code. As gimple gets rid of trees, we handle those in the
front end. So, I don't think that will be a problem.
Diego.
next prev parent reply other threads:[~2011-03-23 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 14:47 Diego Novillo
2011-03-23 14:53 ` Richard Guenther
2011-03-23 15:11 ` Diego Novillo
2011-03-23 16:39 ` Jan Hubicka
2011-03-23 16:49 ` Diego Novillo [this message]
2011-03-23 17:58 ` Diego Novillo
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=AANLkTikbCEPbRuoaY8gYrzDputetd3A8VgA+yigrXpUc@mail.gmail.com \
--to=dnovillo@google.com \
--cc=crowl@google.com \
--cc=gcc@gnu.org \
--cc=hubicka@ucw.cz \
--cc=jh@suse.cz \
--cc=rguenther@suse.de \
/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).