From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] LLVM for plan 9?
Date: Tue, 31 Aug 2010 15:21:57 -0700 [thread overview]
Message-ID: <AANLkTi=kXboOHDYfGeq+ZNTyv83M5YXRP+NvcQ5d2eX6@mail.gmail.com> (raw)
In-Reply-To: <20100831215232.B79505B89@mail.bitblocks.com>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
On Tue, Aug 31, 2010 at 2:52 PM, Bakul Shah
<bakul+plan9@bitblocks.com<bakul%2Bplan9@bitblocks.com>
> wrote:
> On Tue, 31 Aug 2010 14:03:41 PDT David Leimbach <leimy2k@gmail.com>
> > On Tue, Aug 31, 2010 at 1:59 PM, Ori Bernstein <ori@eigenstate.org>
> wrote:
> >
> > > LLVM is written in C++, so you'd need C++ support on plan 9 first.
> Probably
> > > the easiest way to do that would be to add support for plan 9 binaries
> to
> > > clang, and cross-compile llvm for plan 9 with itself.
> > >
> > >
> > Yep. I was thinking a cross compile of clang to Plan 9 would be the
> > starting point once LLVM is self-hosting (Is it?)
>
> You can do this:
>
> $ clang -c -emit-llvm foo.c -o foo.bc # llvm format output
> $ llc -march=c foo.bc -o bar.c # C output
>
> No idea if the resulting .c file is compilable with plan9 C!
> For a real port you'd need to add plan9 a.out format support
> to llvm. Or add ELF support to plan9 :-)
>
> > Likewise. In the meantime it'd be nice to be able to build even just a
> > cross compiler to target Plan 9 :-).
>
> I am interested.
>
>
I hadn't thought about that... interesting.
[-- Attachment #2: Type: text/html, Size: 1579 bytes --]
prev parent reply other threads:[~2010-08-31 22:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 16:10 David Leimbach
2010-08-31 18:33 ` Nick LaForge
2010-08-31 19:48 ` David Leimbach
2010-08-31 21:31 ` Nick LaForge
2010-08-31 22:21 ` David Leimbach
2010-08-31 22:24 ` Nick LaForge
2010-08-31 20:56 ` EBo
2010-08-31 20:59 ` Ori Bernstein
2010-08-31 21:03 ` David Leimbach
2010-08-31 21:52 ` Bakul Shah
2010-08-31 22:21 ` David Leimbach [this message]
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='AANLkTi=kXboOHDYfGeq+ZNTyv83M5YXRP+NvcQ5d2eX6@mail.gmail.com' \
--to=leimy2k@gmail.com \
--cc=9fans@9fans.net \
/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).