From: "Chris Li" <sparse@chrisli.org>
To: Sanghyeon Seo <sanxiyn@gmail.com>
Cc: llvmdev@cs.uiuc.edu, linux-sparse@vger.kernel.org
Subject: Re: Sparse and LLVM
Date: Wed, 27 Dec 2006 03:15:33 -0800 [thread overview]
Message-ID: <70318cbf0612270315p483df383l6d91ca0280a0af27@mail.gmail.com> (raw)
In-Reply-To: <5b0248170612270101o14ad99e0r897fbffdb41e3009@mail.gmail.com>
It is on my todo list, I even have some half baked patches try to do
that.
Converting from sparse linearized code to llvm byte code should
be very straight forward. Like llvm, the sparse pesudo stay in SSA
from. The only tricky part is GEP, sparse convert member deference
to ptr + constant + type cast on the symbol expand stage. Even before
linearization. It is still doable by guesting the type plus offset. I have
some idea how to preserve that information in sparse but I haven't complete
it.
If you try to write a sparse to llvm byte code converter, please start
from the linearized instructions. It will save you a lot of work.
Chris
On 12/27/06, Sanghyeon Seo <sanxiyn@gmail.com> wrote:
> I can't be the first person to think of this, can I? But I couldn't
> locate any reference on this combination. If you know of one, please
> tell me.
>
> Sparse: http://kernel.org/pub/linux/kernel/people/josh/sparse/
> LLVM: http://llvm.org/
>
> So, you may expect compile-llvm.c in a few days. :)
>
> --
> Seo Sanghyeon
> -
> To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2006-12-27 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-27 9:01 Sparse and LLVM Sanghyeon Seo
2006-12-27 11:15 ` Chris Li [this message]
2006-12-28 18:47 ` Reid Spencer
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=70318cbf0612270315p483df383l6d91ca0280a0af27@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=llvmdev@cs.uiuc.edu \
--cc=sanxiyn@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 NNTP newsgroup(s).