9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Joe M <joe9mail@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Porting Idris to 9front
Date: Fri, 13 Jan 2017 07:05:25 -0700	[thread overview]
Message-ID: <20170113140525.GB24399@master> (raw)
In-Reply-To: <1484286924.1672885.846353336.21E2AFA2@webmail.messagingengine.com>

>
> Don't you need GHC to compile Idris?

http://docs.idris-lang.org/en/latest/faq/faq.html#when-will-idris-be-self-hosting

I have the posix version of the rts working on 9front. The default C
backend generated code compiled and runs on 9front. I generated the c
code on linux though.

As a next step, I want to take it further and make the rts and backend
work with the 9front native C compiler/linker. I presume that this
will help make it easy to FFI with the native C libraries (bio,
thread, etc.) and stay closer to the plan 9 libraries' behaviour.

> Afaik, there is no Plan 9 port of GHC. And GHC is self hosted. Perhaps
> one should approach it by creating a plan 9 binary from another OS and
> use that to compile GHC?

That is a good idea. Native GHC on 9front seems to be a daunting task
as the GHC IO manager's behaviour might not be compatible with the
9front syscall behaviour, imho. But, I have no clue of the GHC
internals, so, it might be an easy task.

Maybe, ghc can run with the linux-emu package?

Thanks



  reply	other threads:[~2017-01-13 14:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13  3:29 Joe M
2017-01-13  5:55 ` Ramakrishnan Muthukrishnan
2017-01-13 14:05   ` Joe M [this message]
2017-01-13 14:56     ` Giacomo Tesio
2017-01-13 16:54       ` Joe M
2017-01-14 19:32     ` Ramakrishnan Muthukrishnan
2017-01-14 20:18       ` Ori Bernstein
2017-01-15  2:12         ` Ramakrishnan Muthukrishnan
2017-01-13  6:19 ` Sean Callanan
2017-01-13  8:50 ` Skip Tavakkolian
2017-01-13 13:47   ` Joe M

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=20170113140525.GB24399@master \
    --to=joe9mail@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).