From: "Christopher Li" <sparse@chrisli.org>
To: Linux-Sparse <linux-sparse@vger.kernel.org>,
Alexey Zaytsev <alexey.zaytsev@gmail.com>,
Josh Triplett <josh@freedesktop.org>
Subject: [0/2] RFC: sparse bytecode writer
Date: Wed, 3 Sep 2008 22:34:21 -0700 [thread overview]
Message-ID: <70318cbf0809032234i6b57d5b9i3bb4be11e824898e@mail.gmail.com> (raw)
Hi,
I have been hacking on the sparse code dumper for a while.
Recently there seems some interested in this, so I resurrect
my patches.
The dumper works on the native C structure. It convert the pointer
inside the struct into index numbers. Hopefully on loading, the
same pointer traverse can convert the index back to object
pointer.
Currently there is no attempt to compress the C structure it
writes. So the result is huge, about 50x compare to the stripped
.o file on i386. But it give a very good idea how much memory.
It needs to load such an object file though.
the reader is not ready yet.
Chris
reply other threads:[~2008-09-04 5:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=70318cbf0809032234i6b57d5b9i3bb4be11e824898e@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=alexey.zaytsev@gmail.com \
--cc=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
/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 NNTP newsgroup(s).