From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 27 Jul 2015 14:44:29 +0100 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7b6700df8850c3051bdb8df5 Subject: Re: [9fans] Harvey OS: A new OS inspired heavily by Plan 9 Topicbox-Message-UUID: 63e064d4-ead9-11e9-9d60-3106f5b1d025 --047d7b6700df8850c3051bdb8df5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 27 July 2015 at 13:08, Aram H=C4=83v=C4=83rneanu wrote: > 'd expect GCC compiling Plan 9 at a speed reasonably comparable to kencc. I used gcc for one of my own OS projects years ago, without all the #include crud. It is slow. For one thing, it still(!) produces textual assembly code (because the PDP-11 compiler did that) which must then be assembled. --047d7b6700df8850c3051bdb8df5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 27 July 2015 at 13:08, Aram H=C4=83v=C4=83rneanu <<= a href=3D"mailto:aram.h@mgk.ro" target=3D"_blank">aram.h@mgk.ro> wrote:
'd expect GCC compiling Pl= an 9 at a speed reasonably comparable to kencc.

I use= d gcc for one of my own OS projects years ago, without all the #include cru= d.
It is slow. For one thing, it still(!) p= roduces textual assembly code (because the PDP-11 compiler did that)
<= div class=3D"gmail_extra">which must then be assembled.

--047d7b6700df8850c3051bdb8df5--