From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 From: Skip Tavakkolian Date: Sat, 27 Oct 2018 00:24:39 -0700 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="000000000000435d96057930bbcf" Subject: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: edf80b5e-ead9-11e9-9d60-3106f5b1d025 --000000000000435d96057930bbcf Content-Type: text/plain; charset="UTF-8" Saw this go by on twitter; others here will find it interesting: https://www.geeklan.co.uk/files/oshug69-Miller-criscv.pdf discussion on Ycombinator https://news.ycombinator.com/item?id=18308255 --000000000000435d96057930bbcf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Saw this go by on twitte= r; others here will find it interesting:

--000000000000435d96057930bbcf-- From mboxrd@z Thu Jan 1 00:00:00 1970 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> References: From: Sean Hinchee Message-ID: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> Date: Sat, 27 Oct 2018 13:24:30 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ee068652-ead9-11e9-9d60-3106f5b1d025 On 10/27/18 2:24 AM, Skip Tavakkolian wrote: > Saw this go by on twitter; others here will find it interesting: > > https://www.geeklan.co.uk/files/oshug69-Miller-criscv.pdf > > discussion on Ycombinator > > https://news.ycombinator.com/item?id=18308255 > > Is the source code for this hosted anywhere publicly in a vcs or similar? I'd love to peruse it. From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> From: hiro <23hiro@gmail.com> Date: Sat, 27 Oct 2018 20:45:14 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ee0aa250-ead9-11e9-9d60-3106f5b1d025 never saw the nios2 community port, where is that? On 10/27/18, Sean Hinchee wrote: > On 10/27/18 2:24 AM, Skip Tavakkolian wrote: >> Saw this go by on twitter; others here will find it interesting: >> >> https://www.geeklan.co.uk/files/oshug69-Miller-criscv.pdf >> >> discussion on Ycombinator >> >> https://news.ycombinator.com/item?id=18308255 >> >> > > Is the source code for this hosted anywhere publicly in a vcs or > similar? I'd love to peruse it. > > > From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> In-Reply-To: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> From: Richard Miller <9fans@hamnavoe.com> Date: Sun, 28 Oct 2018 11:32:06 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ee0edf28-ead9-11e9-9d60-3106f5b1d025 On Sat, 27 Oct 2018 at 19:25, Sean Hinchee wrote: > Is the source code for this hosted anywhere publicly in a vcs or > similar? I'd love to peruse it. On 27/10/2018, Sean Hinchee wrote: > Is the source code for this hosted anywhere publicly in a vcs or > similar? I'd love to peruse it. > I've asked David du Colombier to put updates on 9p.io in /sources/contrib/miller/riscv.tar That's for Plan 9 use. I should also configure a version to run on posix-type systems and put that on github. Work in progress warning: floating point support in linker is not done, and there are probably code generation bugs. I've just added an 8 megabyte hyper-ram chip to the fpga board which hosts my riscv soft-cpu, so I should soon be able to test more thoroughly by compiling the compiler through itself on bare-metal riscv. From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> In-Reply-To: From: Richard Miller <9fans@hamnavoe.com> Date: Sun, 28 Oct 2018 11:38:16 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ee13081e-ead9-11e9-9d60-3106f5b1d025 On Sat, 27 Oct 2018 at 19:45, hiro <23hiro@gmail.com> wrote: > > never saw the nios2 community port, where is that? I presented it at IWP9 Madrid in 2011. Nobody seemed very interested so I didn't put it on contrib. I can resurrect a copy if you like. From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnold@skeeve.com Message-Id: <201810281241.w9SCfOLH008760@freefriends.org> Date: Sun, 28 Oct 2018 06:41:24 -0600 To: 9fans@9fans.net References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ee16fe88-ead9-11e9-9d60-3106f5b1d025 Richard Miller <9fans@hamnavoe.com> wrote: > That's for Plan 9 use. I should also configure a version to run on > posix-type systems and put that on github. Is there a standalone version of the Plan 9 C compiler for *nix for x86 / x86_64? I'm looking for something easy to bring up and install to use an an additional compiler for testing a Free Software project. Thanks, Arnold From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> <201810281241.w9SCfOLH008760@freefriends.org> In-Reply-To: <201810281241.w9SCfOLH008760@freefriends.org> From: Skip Tavakkolian Date: Sun, 28 Oct 2018 06:55:55 -0700 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="0000000000009aa2bb05794a503f" Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ee24f844-ead9-11e9-9d60-3106f5b1d025 --0000000000009aa2bb05794a503f Content-Type: text/plain; charset="UTF-8" Inferno sources include kencc that build on the target os/arch. On Sun, Oct 28, 2018, 5:41 AM wrote: > Richard Miller <9fans@hamnavoe.com> wrote: > > > That's for Plan 9 use. I should also configure a version to run on > > posix-type systems and put that on github. > > Is there a standalone version of the Plan 9 C compiler for *nix > for x86 / x86_64? > > I'm looking for something easy to bring up and install to use an > an additional compiler for testing a Free Software project. > > Thanks, > > Arnold > > --0000000000009aa2bb05794a503f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Inferno sources include kencc that build on the targ= et os/arch.

On Sun, Oct = 28, 2018, 5:41 AM <arnold@skeeve.com> wrote:
Richard Miller <9fans@hamnavoe.com>= ; wrote:

> That's for Plan 9 use.=C2=A0 I should also configure a version to = run on
> posix-type systems and put that on github.

Is there a standalone version of the Plan 9 C compiler for *nix
for x86 / x86_64?

I'm looking for something easy to bring up and install to use an
an additional compiler for testing a Free Software project.

Thanks,

Arnold

--0000000000009aa2bb05794a503f-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> <201810281241.w9SCfOLH008760@freefriends.org> In-Reply-To: From: Charles Forsyth Date: Sun, 28 Oct 2018 15:28:52 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="000000000000cb5be005794b9cd2" Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ee33dcd8-ead9-11e9-9d60-3106f5b1d025 --000000000000cb5be005794b9cd2 Content-Type: text/plain; charset="UTF-8" He wants something I think that generates code that will run on unixy systems, and there isn't one, except in specialised ways. On Sun, 28 Oct 2018 at 14:20, Skip Tavakkolian wrote: > Inferno sources include kencc that build on the target os/arch. > > On Sun, Oct 28, 2018, 5:41 AM wrote: > >> Richard Miller <9fans@hamnavoe.com> wrote: >> >> > That's for Plan 9 use. I should also configure a version to run on >> > posix-type systems and put that on github. >> >> Is there a standalone version of the Plan 9 C compiler for *nix >> for x86 / x86_64? >> >> I'm looking for something easy to bring up and install to use an >> an additional compiler for testing a Free Software project. >> >> Thanks, >> >> Arnold >> >> --000000000000cb5be005794b9cd2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
He wants something I think that generates code that will r= un on unixy systems, and there isn't one, except in specialised ways.
On Sun, 28 Oct 2018 at = 14:20, Skip Tavakkolian <s= kip.tavakkolian@gmail.com> wrote:
--000000000000cb5be005794b9cd2-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <1540752526.3238554.1557457560.2E0A981E@webmail.messagingengine.com> From: David du Colombier <0intro@gmail.com> To: 9fans@9fans.net MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" Date: Sun, 28 Oct 2018 19:48:46 +0100 In-Reply-To: References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> <201810281241.w9SCfOLH008760@freefriends.org> Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ee38016e-ead9-11e9-9d60-3106f5b1d025 Richard Miller's RISC-V compiler suite is now available on 9p.io: % srv -nq tcp!9p.io sources /n/sources % ls -l /n/sources/contrib/miller/riscv.tar https://9p.io/sources/contrib/miller/riscv.tar -- David du Colombier From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable From: Steve Simon Mime-Version: 1.0 (1.0) Date: Sun, 28 Oct 2018 19:03:26 +0000 Message-Id: <641BE06D-6B4B-4E30-B8D7-DAD62914BC52@quintile.net> References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> <201810281241.w9SCfOLH008760@freefriends.org> <1540752526.3238554.1557457560.2E0A981E@webmail.messagingengine.com> In-Reply-To: <1540752526.3238554.1557457560.2E0A981E@webmail.messagingengine.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: eec78302-ead9-11e9-9d60-3106f5b1d025 hi, also maybe of interest, charles ported the plan9 c compiler to the atmel at3= 2mega. i asked him for a copy but sadly the project i had foundered. -Steve=20 > On 28 Oct 2018, at 6:48 pm, David du Colombier <0intro@gmail.com> wrote: >=20 > Richard Miller's RISC-V compiler suite is now available on 9p.io: >=20 > % srv -nq tcp!9p.io sources /n/sources > % ls -l /n/sources/contrib/miller/riscv.tar >=20 > https://9p.io/sources/contrib/miller/riscv.tar >=20 > --=20 > David du Colombier From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> From: hiro <23hiro@gmail.com> Date: Sun, 28 Oct 2018 20:23:50 +0100 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ee473058-ead9-11e9-9d60-3106f5b1d025 On 10/28/18, Richard Miller <9fans@hamnavoe.com> wrote: > On Sat, 27 Oct 2018 at 19:45, hiro <23hiro@gmail.com> wrote: >> >> never saw the nios2 community port, where is that? > > I presented it at IWP9 Madrid in 2011. Nobody seemed very interested > so I didn't put it on contrib. I can resurrect a copy if you like. > > yeah, i think it's interesting. i played with nios2 and actually really liked it. From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <641BE06D-6B4B-4E30-B8D7-DAD62914BC52@quintile.net> References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> <201810281241.w9SCfOLH008760@freefriends.org> <1540752526.3238554.1557457560.2E0A981E@webmail.messagingengine.com> <641BE06D-6B4B-4E30-B8D7-DAD62914BC52@quintile.net> From: Lucio De Re Date: Mon, 29 Oct 2018 15:02:26 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: eed89246-ead9-11e9-9d60-3106f5b1d025 I think I have sources for the z[acl] suite somewhere. You make it sound like maybe I should give them back to Charles :-). Lucio. On 10/28/18, Steve Simon wrote: > hi, > > also maybe of interest, charles ported the plan9 c compiler to the atmel > at32mega. i asked him for a copy but sadly the project i had foundered. > > -Steve > > >> On 28 Oct 2018, at 6:48 pm, David du Colombier <0intro@gmail.com> wrote: >> >> Richard Miller's RISC-V compiler suite is now available on 9p.io: >> >> % srv -nq tcp!9p.io sources /n/sources >> % ls -l /n/sources/contrib/miller/riscv.tar >> >> https://9p.io/sources/contrib/miller/riscv.tar >> >> -- >> David du Colombier > > > -- Lucio De Re 2 Piet Retief St Kestell (Eastern Free State) 9860 South Africa Ph.: +27 58 653 1433 Cell: +27 83 251 5824 FAX: +27 58 653 1435 From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> <201810281241.w9SCfOLH008760@freefriends.org> <1540752526.3238554.1557457560.2E0A981E@webmail.messagingengine.com> <641BE06D-6B4B-4E30-B8D7-DAD62914BC52@quintile.net> From: Richard Miller <9fans@hamnavoe.com> Date: Mon, 29 Oct 2018 14:07:05 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="00000000000088fb2305795e958a" Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: eedd9f8e-ead9-11e9-9d60-3106f5b1d025 --00000000000088fb2305795e958a Content-Type: text/plain; charset="UTF-8" > I think I have sources for the z[acl] suite somewhere. You make it > sound like maybe I should give them back to Charles > What architecture is that for? I picked 'z' for riscv hoping there wasn't a collision, but I can change it. --00000000000088fb2305795e958a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I think I have sources for the z[acl] su= ite somewhere. You make it
sound like maybe I should give them back to Charles=C2=A0

What architecture is that for?=C2=A0 I pic= ked 'z' for riscv hoping there wasn't a collision, but I can ch= ange it.
=C2=A0
--00000000000088fb2305795e958a-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> <201810281241.w9SCfOLH008760@freefriends.org> <1540752526.3238554.1557457560.2E0A981E@webmail.messagingengine.com> <641BE06D-6B4B-4E30-B8D7-DAD62914BC52@quintile.net> From: Lucio De Re Date: Mon, 29 Oct 2018 18:13:39 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: eee27b76-ead9-11e9-9d60-3106f5b1d025 AVR, and if I were to weigh in I'd say that its presence in Inferno may justify you changing your choice. I guess Charles did precisely as you did, he probably ought to rename too, so that "z" can be kept as interim for the next architecture :-). Lucio. On 10/29/18, Richard Miller <9fans@hamnavoe.com> wrote: >> I think I have sources for the z[acl] suite somewhere. You make it >> sound like maybe I should give them back to Charles >> > > What architecture is that for? I picked 'z' for riscv hoping there wasn't > a collision, but I can change it. > -- Lucio De Re 2 Piet Retief St Kestell (Eastern Free State) 9860 South Africa Ph.: +27 58 653 1433 Cell: +27 83 251 5824 FAX: +27 58 653 1435 From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> <201810281241.w9SCfOLH008760@freefriends.org> <1540752526.3238554.1557457560.2E0A981E@webmail.messagingengine.com> <641BE06D-6B4B-4E30-B8D7-DAD62914BC52@quintile.net> In-Reply-To: From: Charles Forsyth Date: Mon, 29 Oct 2018 16:26:55 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="0000000000004115490579608af7" Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: eee76eec-ead9-11e9-9d60-3106f5b1d025 --0000000000004115490579608af7 Content-Type: text/plain; charset="UTF-8" It's z because the Atmel AVR is the last thing you'd want to use. (As usual, once you've got C going, it's ok, except for the design bugs.) They were in the Berkeley mote, which we worked on years ago, later on custom hardware, but always with completely different software from Berkeley's. I had little processes. The loader minimised register saves on interrupts. I had a chart somewhere with the available non-unicode letters. On Mon, 29 Oct 2018 at 14:07, Richard Miller <9fans@hamnavoe.com> wrote: > > I think I have sources for the z[acl] suite somewhere. You make it >> sound like maybe I should give them back to Charles >> > > What architecture is that for? I picked 'z' for riscv hoping there wasn't > a collision, but I can change it. > > --0000000000004115490579608af7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
It's z because the Atmel AVR is the last thing you'= ;d want to use. (As usual, once you've got C going, it's ok, except= for the design bugs.)
They were in the Berkeley mote, which we worked = on years ago, later on custom hardware, but always with completely differen= t software from Berkeley's.
I had little processes. The loade= r minimised register saves on interrupts.

I had a = chart somewhere with the available non-unicode letters.

On Mon, 29 Oct 2018 at 14:07, Richa= rd Miller <9fans@hamnavoe.com&= gt; wrote:

I think I have sources for the z[acl] suite somewhere. You make = it
sound like maybe I should give them back to Charles=C2=A0

What architecture is that for?=C2=A0 I pic= ked 'z' for riscv hoping there wasn't a collision, but I can ch= ange it.
=C2=A0
--0000000000004115490579608af7-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> <201810281241.w9SCfOLH008760@freefriends.org> <1540752526.3238554.1557457560.2E0A981E@webmail.messagingengine.com> <641BE06D-6B4B-4E30-B8D7-DAD62914BC52@quintile.net> From: Lucio De Re Date: Tue, 30 Oct 2018 06:52:37 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: eeec5664-ead9-11e9-9d60-3106f5b1d025 On 10/29/18, Charles Forsyth wrote: > It's z because the Atmel AVR is the last thing you'd want to use. (As > usual, once you've got C going, it's ok, except for the design bugs.) Sadly, some of the Atmel kit I'd like to play with is no longer supported, the CPUs are nowhere to be sourced from in reasonable quantities. So that's yet another nail in that coffin. > I had a chart somewhere with the available non-unicode letters. > Is there a technical reason (beside fonts that do not cover them) not to use a Unicode values for the first letter? We could perhaps grab a bunch of unassigned codes and design glyphs for them? Use them as logos? Lucio. From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 30 Oct 2018 02:32:50 -0700 From: Anthony Martin To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20181030093250.GA28044@alice> References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> <201810281241.w9SCfOLH008760@freefriends.org> <1540752526.3238554.1557457560.2E0A981E@webmail.messagingengine.com> <641BE06D-6B4B-4E30-B8D7-DAD62914BC52@quintile.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: eef0963e-ead9-11e9-9d60-3106f5b1d025 Charles Forsyth once said: > I had a chart somewhere with the available non-unicode letters. I made one a few years ago. It's at http://pbrane.org/comp.html I just updated it with a suggestion for the RISC-V letters. Anthony From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <513773d964eb01c4ce7f38f1b48e74f4@hamnavoe.com> To: 9fans@9fans.net From: Richard Miller <9fans@hamnavoe.com> Date: Tue, 30 Oct 2018 10:31:50 +0000 In-Reply-To: <20181030093250.GA28044@alice> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: eef547c4-ead9-11e9-9d60-3106f5b1d025 > I just updated it with a suggestion for the RISC-V letters. How about i for rIscv32 and j for riscv64 (one more than i)? I used n for nios2. na and aux/na commands are distinct, and I wouldn't expect SYM53C8XX microcode and nios2 object code to appear in the same context. > Is there a technical reason (beside fonts that do not cover them) not > to use a Unicode values for the first letter? They're a bit harder to produce on the keyboard. From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <1540903281.1546324.1559542232.514E7438@webmail.messagingengine.com> From: Ethan Gardener To: 9fans@9fans.net MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" In-Reply-To: References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> <201810281241.w9SCfOLH008760@freefriends.org> <1540752526.3238554.1557457560.2E0A981E@webmail.messagingengine.com> <641BE06D-6B4B-4E30-B8D7-DAD62914BC52@quintile.net> Date: Tue, 30 Oct 2018 12:41:21 +0000 Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: eefc4ff6-ead9-11e9-9d60-3106f5b1d025 On Tue, Oct 30, 2018, at 4:52 AM, Lucio De Re wrote: > > Is there a technical reason (beside fonts that do not cover them) not > to use a Unicode values for the first letter? Not a major reason, but at least one of Plan 9's build tools compares them as C chars, and would need to be fixed. I can't remember which one it is right now. -- Progress might have been all right once, but it has gone on too long -- Ogden Nash From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Simon Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Tue, 30 Oct 2018 14:55:31 +0000 Message-Id: <286F8C93-4120-4186-9960-0A0A91ABFDAA@quintile.net> References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> <201810281241.w9SCfOLH008760@freefriends.org> <1540752526.3238554.1557457560.2E0A981E@webmail.messagingengine.com> <641BE06D-6B4B-4E30-B8D7-DAD62914BC52@quintile.net> <1540903281.1546324.1559542232.514E7438@webmail.messagingengine.com> In-Reply-To: <1540903281.1546324.1559542232.514E7438@webmail.messagingengine.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ef057946-ead9-11e9-9d60-3106f5b1d025 hi, i have long wanted the table of compiler letters an the binary dir names the= y relate to to be defined in a textfile somewhere (/lib/cpus maybe). current= ly there are bits in mkfiles and some hard coded tables in cpp and c86 etc.=20= when i wrote mkmk i just added another copy of the same table. -Steve > On 30 Oct 2018, at 12:41 pm, Ethan Gardener wrote: >=20 >> On Tue, Oct 30, 2018, at 4:52 AM, Lucio De Re wrote: >>=20 >> Is there a technical reason (beside fonts that do not cover them) not >> to use a Unicode values for the first letter?=20 >=20 > Not a major reason, but at least one of Plan 9's build tools compares them= as C chars, and would need to be fixed. I can't remember which one it is r= ight now. >=20 > --=20 > Progress might have been all right once, but it has gone on too long -- Og= den Nash From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> <201810281241.w9SCfOLH008760@freefriends.org> <1540752526.3238554.1557457560.2E0A981E@webmail.messagingengine.com> <641BE06D-6B4B-4E30-B8D7-DAD62914BC52@quintile.net> <20181030093250.GA28044@alice> In-Reply-To: <20181030093250.GA28044@alice> From: Charles Forsyth Date: Tue, 30 Oct 2018 15:06:32 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="000000000000a455d8057973880a" Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ef0a6f32-ead9-11e9-9d60-3106f5b1d025 --000000000000a455d8057973880a Content-Type: text/plain; charset="UTF-8" This was my old list for comparison .a ar(1) archive .b bc(1), limbo source .c C source .d dc(1) .e -- was efl .f fortran .g -- there was a gc? .h C include .i na(8) output .j .k ka, kc, kl .l lc(1), lex .m mc(1), limbo module source .n na(8) .o unix object files .p pascal source? .q qa, qc, ql power .r rc(1), ratfor .s assembler source .t tc, with 5a/5l arm (thumb) .u uc sparc64 .v va, vc, vl mips .w wc(1) .x -- old xa, xc, xl .y -- yacc .z za, zc, zl [VN atmel compiler] .0 0[acl] spim .1 1a, 1c, 1l 68010 .2 2[acl] 68020 .3 -- free (perhaps sh-3) .4 64-bit mips? .5 5a, 5c, 5l arm .6 6a, 6c, 6l amd64 .7 7a, 7c, 7l arm64 .8 8a, 8c, 8l 386 .9 p9p, 9[acl] power64 On Tue, 30 Oct 2018 at 09:35, Anthony Martin wrote: > Charles Forsyth once said: > > I had a chart somewhere with the available non-unicode letters. > > I made one a few years ago. It's at http://pbrane.org/comp.html > > I just updated it with a suggestion for the RISC-V letters. > > Anthony > > --000000000000a455d8057973880a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
This was my old list for comparison
=

.a ar= (1) archive
.b bc(1), limb= o source
.c C source
=
.d dc(1)
.e -- was efl
.f fortran
.g -- there was a gc?
.h C= include
.i na(8) output
.j
.k ka, kc, kl<= /div>
.l lc(1), lex
.m= mc(1), limbo module source
.n na(8)
.o unix object files
.p pascal source?
.q qa, qc, ql power
.r rc(1), ratfor
.s= assembler source
.t tc, with 5a/5l arm (thumb)
.u uc sparc64
.v va, vc, vl mips
.w wc(1)
.x -- old xa, xc, xl
.y<= span style=3D"white-space:pre"> -- yacc
.z za, zc, zl [VN atmel compiler]
.0 0[acl] spim
.1 1a, 1c, 1l 68010
.2 2[acl] 68020
.3 -- free (perhaps sh-3)
.4 64-bit mips?
.5 5a, 5c, 5l arm
.6 6a, 6c, 6l= amd64
.7 7a, 7c, 7l ar= m64
.8 8a, 8c, 8l 386
.9 p9p, 9[acl] power64


On Tue, 30 Oct 2018 at 09:35, Anthony Martin <ality@pbrane.org> wrote:
Charles Forsyth <charles.forsyth@gmail.com> once said:
> I had a chart somewhere with the available non-unicode letters.

I made one a few years ago. It's at http://pbrane.org/comp.html
I just updated it with a suggestion for the RISC-V letters.

=C2=A0 Anthony

--000000000000a455d8057973880a-- From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 30 Oct 2018 15:15:54 +0000 From: "Brian L. Stuart" To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <857020832.6276700.1540912554946@mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit References: <857020832.6276700.1540912554946.ref@mail.yahoo.com> Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ef0f11e0-ead9-11e9-9d60-3106f5b1d025 On Tue, 10/30/18, Richard Miller <9fans@hamnavoe.com> wrote: > > Is there a technical reason (beside fonts that do not cover them) not > > to use a Unicode values for the first letter? > > They're a bit harder to produce on the keyboard. Especially if you're at a VT-220 on the console and can't run rio. Don't laugh. I actually have a VT-220 on my file server. BLS From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> <201810281241.w9SCfOLH008760@freefriends.org> <1540752526.3238554.1557457560.2E0A981E@webmail.messagingengine.com> <641BE06D-6B4B-4E30-B8D7-DAD62914BC52@quintile.net> <1540903281.1546324.1559542232.514E7438@webmail.messagingengine.com> In-Reply-To: <1540903281.1546324.1559542232.514E7438@webmail.messagingengine.com> From: Charles Forsyth Date: Tue, 30 Oct 2018 15:16:54 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="000000000000b361d5057973ad54" Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ef12b1d8-ead9-11e9-9d60-3106f5b1d025 --000000000000b361d5057973ad54 Content-Type: text/plain; charset="UTF-8" I used Ka/Kb/Kc (upper case) for my Fairchild Clipper port, but that doesn't work on case-insensitive file systems. I did once make the changes for unicode, but again there can be problems with non-Plan9 file systems, even now. On Tue, 30 Oct 2018 at 12:43, Ethan Gardener wrote: > On Tue, Oct 30, 2018, at 4:52 AM, Lucio De Re wrote: > > > > Is there a technical reason (beside fonts that do not cover them) not > > to use a Unicode values for the first letter? > > Not a major reason, but at least one of Plan 9's build tools compares them > as C chars, and would need to be fixed. I can't remember which one it is > right now. > > -- > Progress might have been all right once, but it has gone on too long -- > Ogden Nash > > --000000000000b361d5057973ad54 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I used Ka/Kb/Kc (upper case) for my Fairchild Clipper port= , but that doesn't work on case-insensitive file systems.
I did onc= e make the changes for unicode, but again there can be problems with non-Pl= an9 file systems, even now.



On Tue, 30 Oct 2018 at 12:43, Eth= an Gardener <ee= kee57@fastmail.fm> wrote:
On= Tue, Oct 30, 2018, at 4:52 AM, Lucio De Re wrote:
=C2=A0>
> Is there a technical reason (beside fonts that do not cover them) not<= br> > to use a Unicode values for the first letter?

Not a major reason, but at least one of Plan 9's build tools compares t= hem as C chars, and would need to be fixed.=C2=A0 I can't remember whic= h one it is right now.

--
Progress might have been all right once, but it has gone on too long -- Ogd= en Nash

--000000000000b361d5057973ad54-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Simon Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Tue, 30 Oct 2018 15:37:24 +0000 Message-Id: <818CB4E0-F4BF-4723-97A1-088101823EC8@quintile.net> References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> <201810281241.w9SCfOLH008760@freefriends.org> <1540752526.3238554.1557457560.2E0A981E@webmail.messagingengine.com> <641BE06D-6B4B-4E30-B8D7-DAD62914BC52@quintile.net> <1540903281.1546324.1559542232.514E7438@webmail.messagingengine.com> In-Reply-To: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ef173b68-ead9-11e9-9d60-3106f5b1d025 There once was a vax port but i don=E2=80=99t know what its letter was. From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <151626de3a5ff350a8acbcf2ffbfbb4e@hamnavoe.com> To: 9fans@9fans.net From: Richard Miller <9fans@hamnavoe.com> Date: Tue, 30 Oct 2018 17:03:06 +0000 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ef1bcff2-ead9-11e9-9d60-3106f5b1d025 > never saw the nios2 community port, where is that? Now on 9p.io in /contrib/miller/nios.tar It's pretty old, probably needs some updating to fit with current libmach and cc. Also no floating point. From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 30 Oct 2018 22:18:54 -0700 From: Anthony Martin To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20181031051854.GA7907@alice> References: <20181030093250.GA28044@alice> <513773d964eb01c4ce7f38f1b48e74f4@hamnavoe.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <513773d964eb01c4ce7f38f1b48e74f4@hamnavoe.com> Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ef29553c-ead9-11e9-9d60-3106f5b1d025 Richard Miller <9fans@hamnavoe.com> once said: > How about i for rIscv32 and j for riscv64 (one more than i)? Or even e for riscv since it's the fifth letter in the alphabet. :) Let me know what you decide and I'll update my table. > I used n for nios2. na and aux/na commands are distinct, and > I wouldn't expect SYM53C8XX microcode and nios2 object code > to appear in the same context. That works but be careful running clean in /sys/src/9/pc after adding the n letter to $OS in /sys/src/mkfile.proto. It will blow away the sd53c8xx.n file and you'll have to get it from the dump. That file is now named sd53c8xx.na over here. Anthony From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <625ae81fb9da92a61ca995c71525f3ad@hamnavoe.com> To: 9fans@9fans.net From: Richard Miller <9fans@hamnavoe.com> Date: Wed, 31 Oct 2018 09:36:54 +0000 In-Reply-To: <20181031051854.GA7907@alice> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ef2d4494-ead9-11e9-9d60-3106f5b1d025 > That works but be careful running clean in /sys/src/9/pc after adding > the n letter to $OS in /sys/src/mkfile.proto. Hadn't thought of that. May also be a risk to nroff files ... From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <1540993348.3930633.1560931072.2D4E9E16@webmail.messagingengine.com> From: Ethan Gardener To: 9fans@9fans.net MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> <201810281241.w9SCfOLH008760@freefriends.org> <1540752526.3238554.1557457560.2E0A981E@webmail.messagingengine.com> <641BE06D-6B4B-4E30-B8D7-DAD62914BC52@quintile.net> <1540903281.1546324.1559542232.514E7438@webmail.messagingengine.com> <818CB4E0-F4BF-4723-97A1-088101823EC8@quintile.net> Date: Wed, 31 Oct 2018 13:42:28 +0000 In-Reply-To: <818CB4E0-F4BF-4723-97A1-088101823EC8@quintile.net> Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ef31369e-ead9-11e9-9d60-3106f5b1d025 On Tue, Oct 30, 2018, at 3:37 PM, Steve Simon wrote: >=20 > There once was a vax port but i don=E2=80=99t know what its letter was. Well, 7 used to be Alpha. I remember someone being very annoyed because he= still had Alpha hardware when the Go team decided to use 7 for Arm64. From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <1540993682.3931792.1560937160.42074B8B@webmail.messagingengine.com> From: Ethan Gardener To: 9fans@9fans.net MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" References: <857020832.6276700.1540912554946.ref@mail.yahoo.com> <857020832.6276700.1540912554946@mail.yahoo.com> In-Reply-To: <857020832.6276700.1540912554946@mail.yahoo.com> Date: Wed, 31 Oct 2018 13:48:02 +0000 Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ef35ab98-ead9-11e9-9d60-3106f5b1d025 On Tue, Oct 30, 2018, at 3:15 PM, Brian L. Stuart wrote: > On Tue, 10/30/18, Richard Miller <9fans@hamnavoe.com> wrote: > > > Is there a technical reason (beside fonts that do not cover them) not > > > to use a Unicode values for the first letter? > > > > They're a bit harder to produce on the keyboard. > > Especially if you're at a VT-220 on the console and can't > run rio. > > Don't laugh. I actually have a VT-220 on my file server. For all the complaints I've made about terminals in the past, I'd love to actually have a terminal or two. :) From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <8408d6ed-c06f-fbc1-6825-4deffef905cf@gmail.com> <201810281241.w9SCfOLH008760@freefriends.org> <1540752526.3238554.1557457560.2E0A981E@webmail.messagingengine.com> <641BE06D-6B4B-4E30-B8D7-DAD62914BC52@quintile.net> <1540903281.1546324.1559542232.514E7438@webmail.messagingengine.com> <818CB4E0-F4BF-4723-97A1-088101823EC8@quintile.net> <1540993348.3930633.1560931072.2D4E9E16@webmail.messagingengine.com> In-Reply-To: <1540993348.3930633.1560931072.2D4E9E16@webmail.messagingengine.com> From: Charles Forsyth Date: Wed, 31 Oct 2018 17:04:36 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="000000000000b8735f0579894c99" Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ef3f544a-ead9-11e9-9d60-3106f5b1d025 --000000000000b8735f0579894c99 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I was the one that replaced Alpha by ARM64 as 7 for Plan 9. On Wed, 31 Oct 2018 at 13:44, Ethan Gardener wrote: > On Tue, Oct 30, 2018, at 3:37 PM, Steve Simon wrote: > > > > There once was a vax port but i don=E2=80=99t know what its letter was. > > Well, 7 used to be Alpha. I remember someone being very annoyed because > he still had Alpha hardware when the Go team decided to use 7 for Arm64. > > --000000000000b8735f0579894c99 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I was the one that replaced Alpha by ARM64 as 7 for Plan 9= .=C2=A0

On Wed, 31 Oct= 2018 at 13:44, Ethan Gardener <e= ekee57@fastmail.fm> wrote:
O= n Tue, Oct 30, 2018, at 3:37 PM, Steve Simon wrote:
>
> There once was a vax port but i don=E2=80=99t know what its letter was= .

Well, 7 used to be Alpha.=C2=A0 I remember someone being very annoyed becau= se he still had Alpha hardware when the Go team decided to use 7 for Arm64.=

--000000000000b8735f0579894c99-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lyndon Nerenberg To: "Brian L. Stuart" , Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-reply-to: <857020832.6276700.1540912554946@mail.yahoo.com> References: <857020832.6276700.1540912554946.ref@mail.yahoo.com> <857020832.6276700.1540912554946@mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <34169.1541811878.1@orthanc.ca> Date: Fri, 9 Nov 2018 17:04:39 -0800 Message-Id: <7aa2beefcb333b94@orthanc.ca> Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ef591466-ead9-11e9-9d60-3106f5b1d025 Brian L. Stuart writes: > Don't laugh. I actually have a VT-220 on my file server. You do a lot of manual code compiling and linking from the serial console of your file server, do you? Then you deserve all the pain that can possibly be inflicted upon you ;-) --lyndon From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 9 Nov 2018 19:28:31 -0800 Message-ID: <5eecb311-fc2d-405e-8c9b-cf1a0bb649e9@email.android.com> In-Reply-To: <7aa2beefcb333b94@orthanc.ca> From: erik quanstrom To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> MIME-Version: 1.0 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller Topicbox-Message-UUID: ef5ce3f2-ead9-11e9-9d60-3106f5b1d025 PGRpdiBkaXI9J2F1dG8nPkkgdHlwaWNhbGx5IHVzZSBDRUMgaW5zdGVhZCBvZiBhIHJlYWwgc2Vy aWFsIGNvbnNvbGUuPGRpdiBkaXI9ImF1dG8iPjxicj48L2Rpdj48ZGl2IGRpcj0iYXV0byI+LSBl cmlrPC9kaXY+PGRpdiBkaXI9ImF1dG8iPjxicj48L2Rpdj48L2Rpdj4=