From: Diego Novillo <dnovillo@google.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Basile Starynkevitch <basile@starynkevitch.net>, gcc@gcc.gnu.org
Subject: Re: Serializing mixed gimple data from a plugin in LTO?
Date: Fri, 25 Mar 2011 12:01:00 -0000 [thread overview]
Message-ID: <AANLkTim3JSN7=fnRXVpUZ4go7h70+UeWj41TpbDRjWdf@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikB2FseW_-JbBPq4SC_R-qE3wnX6Ek=nKmuVmj+@mail.gmail.com>
On Fri, Mar 25, 2011 at 06:06, Richard Guenther
<richard.guenther@gmail.com> wrote:
> You are not allowed to piggy-back on statements but only global things
> like cgraph and varpool. There is no way to transition data from before
> LTO to after associated with statements. And there never will be.
But one could write out a table indexed by gimple statement uid. That
would allow the pass to reconstruct the statement metadata on the way
in.
Diego.
next prev parent reply other threads:[~2011-03-25 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 10:07 Basile Starynkevitch
2011-03-25 10:13 ` Richard Guenther
2011-03-25 12:01 ` Diego Novillo [this message]
2011-03-25 12:17 ` Richard Guenther
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='AANLkTim3JSN7=fnRXVpUZ4go7h70+UeWj41TpbDRjWdf@mail.gmail.com' \
--to=dnovillo@google.com \
--cc=basile@starynkevitch.net \
--cc=gcc@gcc.gnu.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).