From: "Bruce Ellis" <bruce.ellis@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] 9ee
Date: Sat, 11 Aug 2007 14:33:52 +1000 [thread overview]
Message-ID: <775b8d190708102133m225c8426k970125abb79bd384@mail.gmail.com> (raw)
In-Reply-To: <2AFE29E7-7D07-4CEE-8FFD-7841B35CC563@telus.net>
that's right. the only thing that needs a native compiler
is the launcher and Mr Syscall.
9eekern is of course compiled with kencc.
brucee
On 8/11/07, Paul Lalonde <plalonde@telus.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> If I'm reading brucee correctly, he's cross compiling using kencc but
> running natively; there's no "native" compiler involved, just a (very
> old-school seeming) loader program and his system-call thunks. Clever.
>
> Paul
>
> On 10-Aug-07, at 6:41 PM, erik quanstrom wrote:
>
> > On Fri Aug 10 20:45:06 EDT 2007, bruce.ellis@gmail.com wrote:
> >> the only issue is calling in and out, the two thunks. you write
> >> a small bit of assembly language for these, again and again
> >> until you get it right. there are no other compiler clashes.
> >>
> >> brucee
> >
> > sorry. i'm not following at all. are you using ken's compiler?
> >
> > if not, how do you deal with unnamed structures. if so, don't
> > you have to do a lot dealing with object file formats?
> >
> > - erik
> >
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFGvSQLpJeHo/Fbu1wRArcSAKDfCOHwI+pLz7xZRu5Q28zHiiwJkQCfYLaC
> cVRHgmzRNlWvwke4OViFvZ0=
> =dyEw
> -----END PGP SIGNATURE-----
>
next prev parent reply other threads:[~2007-08-11 4:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <775b8d190708101742l7755885du92fc1ac4b84bd4ce@mail.gmail.com>
2007-08-11 1:41 ` erik quanstrom
2007-08-11 2:50 ` Paul Lalonde
2007-08-11 4:33 ` Bruce Ellis [this message]
2007-08-11 5:10 ` Anthony Sorace
2007-08-11 0:14 Bruce Ellis
2007-08-11 0:24 ` erik quanstrom
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=775b8d190708102133m225c8426k970125abb79bd384@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--cc=9fans@cse.psu.edu \
/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).