From: John Floren <john@jfloren.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Can compile Plan9 C compiler for windows10?
Date: Mon, 29 Mar 2021 10:58:04 -0700 [thread overview]
Message-ID: <CAL4LZyi57_bwUL3xf7zJ+n6Pj4oF94fDEkg44wsC1QmF+DR6LQ@mail.gmail.com> (raw)
In-Reply-To: <8c579fdf17c7c275e4d024eb9b39d62a76e55f7a@hey.com>
On Mon, Mar 29, 2021 at 10:47 AM Russ Cox <rsc@swtch.com> wrote:
>
> On March 29, 2021, arnold@skeeve.com wrote:
>
> OK - wasn't kenc ported to Linux for bootstrapping the early
> Go compilers? Is that version general, or not worth my trying to use?
>
>
> The early Go compilers, written in C, were compiled with gcc or clang.
>
> The Plan 9 C compiler was used for the Go runtime's initial
> C implementation, but in that context it was only dealing
> with the self-contained demands of Go itself, not arbitrary C code
> (no standard C library, much of which gawk would need).
>
> Even in that limited context, we spent a frustrating (non-zero)
> amount of time stumbling over bugs.
> Standard C has moved on, and the Plan 9 C compilers have not kept up.
> They're still fine for Plan 9 C code, but given the choice
> I wouldn't throw anything else at them.
>
> Best,
> Russ
> 9fans / 9fans / see discussions + participants + delivery options Permalink
Years back I spent some time getting the 9k kernel compiling with Go's
C compilers. It's been a long time so I don't remember everything I
had to do, but it wasn't a straight-across change and we ended up
deciding that since the Go compilers were being maintained
specifically to compile Go, it wouldn't be a good idea to hitch our
wagon to them lest they make some Go-focused changes which break our
stuff.
john
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4d77cc95ab4ed70c-Ma6467d9eedaa83ac761e35da
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-03-29 17:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 8:13 saif.resun
2021-03-28 9:09 ` Richard Miller
2021-03-28 9:21 ` Sean Hinchee
2021-03-28 13:16 ` saif.resun
2021-03-28 15:08 ` ron minnich
2021-03-29 6:42 ` arnold
2021-03-29 14:04 ` Russ Cox
2021-03-29 14:14 ` arnold
2021-03-29 15:08 ` Charles Forsyth
2021-03-29 17:18 ` arnold
2021-03-29 17:45 ` Russ Cox
2021-03-29 17:55 ` arnold
2021-03-29 17:58 ` John Floren [this message]
2021-03-29 15:15 ` ori
2021-03-28 15:16 ` Paul Lalonde
2021-03-29 4:51 ` Ethan Gardener
2021-03-29 4:57 ` Ethan Gardener
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=CAL4LZyi57_bwUL3xf7zJ+n6Pj4oF94fDEkg44wsC1QmF+DR6LQ@mail.gmail.com \
--to=john@jfloren.net \
--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).