From: Christopher Li <firstname.lastname@example.org>
To: Al Viro <email@example.com>
Cc: Andi Kleen <firstname.lastname@example.org>,
linux kernel mail list <email@example.com>,
Josh Triplett <firstname.lastname@example.org>
Subject: Re: [ANNOUNCE] sparse-0.2-cl2 is now available
Date: Sat, 10 Feb 2007 22:02:55 -0800 [thread overview]
Message-ID: <20070211060255.GA2312@chrisli.org> (raw)
On Sun, Feb 11, 2007 at 05:50:15AM +0000, Al Viro wrote:
> I have some stuff in that direction, but it take some resurrecting...
OK, we should talk.
Here is what I have:
Linearize bytecode writer, which produce the binary linearized code.
The uncompress size is about 10 times the i386 .o file. I don't have
the loader ready to verify it yet. It is aim at fast loading bytecode
and simple, I havn't done much toward optimized the code size.
If we keep it 10 times over head, my home computer can load the full linux
kernel and have some spare for checking.
I am still working on the bytecode loader and linker for merging symbols.
It need to answer the question:
Which file define which function.
Which external symbol does this function use.
Once we get the function user/define chain, it can enable a lot of new checking.
The current linearized code is not very friendly to linking because we
keep abstract declare and real declare as different node. Depend on the
position, the caller will get different node even in one file.
I am going to take out the LKML on later email because discussion is
more sparse specific now.
next prev parent reply other threads:[~2007-02-11 6:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-04 8:53 [ANNOUNCE] sparse-0.2-cl1 is now available Christopher Li
2007-02-10 0:00 ` [ANNOUNCE] sparse-0.2-cl2 " Christopher Li
2007-02-10 17:33 ` Andi Kleen
2007-02-11 5:17 ` Christopher Li
2007-02-11 5:50 ` Al Viro
2007-02-11 6:02 ` Christopher Li [this message]
2007-02-11 10:41 ` Andi Kleen
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.