From: nkavv@physics.auth.gr
To: linux-sparse@vger.kernel.org
Subject: Backend projects for Sparse
Date: Wed, 28 Nov 2007 11:53:00 +0200 [thread overview]
Message-ID: <1196243580.474d3a7c9895b@mail.physics.auth.gr> (raw)
Hi all
i came across Sparse a few months ago and looks really interesting. Now, I have
a few questions regarding the sparse infrastructure:
1) Regarding the intermediate representation dumps that can be generated (via
"test-linearize" i think). Do you support canonical SSA form (as defined in the
classical books/papers)?
2) Is it possible to generate a self-contained IR dump, so that it could be
possible to feed it to external (third-party) code selectors?
In my mind a single C program file (actually read: translation unit) would be
translated to something like the following structure:
struct CTranslationUnit {
struct GlobalVars; // is a List of global variables (scalars, arrays etc)
struct ProcedureList;
}
struct ProcedureList
{
struct LocalVars; // local variable list
List ThreeAddressCodeInstr; // three-address code operations (4-tuples)
}
There a couple of frontends that can do this (the proprietary/no cost for
research only LANCE compiler frontend).
3) What does the c2xml backend exactly do?
4) Is there anyone working on a RISC-like processor backend project. I feel that
if the entire backend can be contained in something like "compile-i386.c" then
it could be even possible to automate the generation of such file from a more
compact specification file. (plus some hand-written intrinsics probably).
5) Is there any documentation covering the API and linked tools to the sparse
library (something more than the man pages)?
6) Sparse looks good. I like the IR dumps a lot. That's a comment ^_^
Kind regards,
Nikolaos Kavvadias
next reply other threads:[~2007-11-28 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 9:53 nkavv [this message]
2007-11-28 18:53 ` Backend projects for Sparse Christopher Li
2007-11-28 19:00 ` Nikolaos Kavvadias
2007-11-28 19:25 ` Christopher Li
2007-11-29 9:09 ` nkavv
2007-11-28 19:45 ` Jeff Garzik
2007-11-28 20:27 ` Christopher Li
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=1196243580.474d3a7c9895b@mail.physics.auth.gr \
--to=nkavv@physics.auth.gr \
--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).