From: Cyber Fonic <cyberfonic@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 C compiler for Xtensa CPUs
Date: Fri, 26 Jul 2019 22:12:43 +1000 [thread overview]
Message-ID: <CALj3Nd3gDva4G=cWgivx5HNccgFYfErusmPSVO0Rbz59xmHb_w@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5h5SE1XweOp4naQzswek4oHXy9JK-oRkyQLLg2zEigZkw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
Does anybody have any suggestions as to what it would take to create a C
compiler for Xtensa (it is basically a 32 bit sorta-like RISC architecture)?
Since C compilers do exist for Xtensa (both Arduino and ESIF) , is it at
all possible to port Plan 9 C compilers using a "host" compiler as a
semi-bootstrap?
Or would it be more effectively to use an existing Plan 9 system, grab the
sources for a similar compiler, e.g. MIPS and start building a Xtensa /
ESP-32 specific one?
On Fri, 26 Jul 2019 at 20:31, Charles Forsyth <charles.forsyth@gmail.com>
wrote:
> I was thinking of doing that since I've got an ESP-32 for some reason
>
> On Fri, Jul 26, 2019 at 7:38 AM Cyber Fonic <cyberfonic@gmail.com> wrote:
>
>> I was reading the post Why Didn't Plan 9 Succeed
>> <https://news.ycombinator.com/item?id=20527650> on Hacker News.
>>
>> Made me think that Plan 9 for IoT system of systems could be viable.
>>
>> To that end, ESP-32 modules look capable enough to run Plan 9, but is
>> there a Plan 9 C compiler for Xtensa ISA CPUs?
>>
>>
[-- Attachment #2: Type: text/html, Size: 1772 bytes --]
next prev parent reply other threads:[~2019-07-26 12:12 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 6:37 Cyber Fonic
2019-07-26 10:02 ` Rodrigo G. López
2019-07-26 10:30 ` Charles Forsyth
2019-07-26 12:04 ` Rodrigo G. López
2019-07-26 12:12 ` Cyber Fonic [this message]
2019-07-26 15:23 ` Charles Forsyth
2019-07-27 9:16 ` Anthony Martin
2019-07-27 11:10 ` Richard Miller
2019-07-27 16:29 ` Anthony Martin
2019-08-07 0:22 ` Charles Forsyth
2019-08-07 8:07 ` Lucio De Re
2019-08-09 14:17 ` Bakul Shah
2019-08-09 14:50 ` Charles Forsyth
2019-08-09 15:50 ` Charles Forsyth
2019-08-09 21:34 ` Charles Forsyth
2019-08-09 21:48 ` Shane Morris
2019-08-09 22:51 ` Bakul Shah
2019-08-09 22:53 ` Skip Tavakkolian
2019-08-10 9:09 ` Cyber Fonic
2019-08-10 9:15 ` Shane Morris
2019-08-10 16:18 ` Charles Forsyth
2019-08-11 18:59 ` Lyndon Nerenberg
2019-08-18 14:10 ` Charles Forsyth
2019-08-18 14:28 ` Richard Miller
2019-08-19 11:51 ` Cyber Fonic
2019-08-19 14:52 ` [9fans] Plan 9 security Ethan Gardener
2019-08-20 13:13 ` Cyber Fonic
2019-08-20 13:28 ` Don A. Bailey
2019-08-23 18:45 ` Ethan Gardener
2019-08-23 19:41 ` Don Bailey
2019-07-26 13:16 [9fans] Plan 9 C compiler for Xtensa CPUs cinap_lenrek
2023-12-04 23:20 David Boddie
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='CALj3Nd3gDva4G=cWgivx5HNccgFYfErusmPSVO0Rbz59xmHb_w@mail.gmail.com' \
--to=cyberfonic@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).