Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller
Richard Miller <9f...@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
Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller
> 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.
Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller
There once was a vax port but i don’t know what its letter was.
Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller
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 > >
Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller
On Tue, 10/30/18, Richard Miller <9f...@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
Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller
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 > >
Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller
hi, i have long wanted the table of compiler letters an the binary dir names they relate to to be defined in a textfile somewhere (/lib/cpus maybe). currently there are bits in mkfiles and some hard coded tables in cpp and c86 etc. 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: > >> 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
Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller
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
Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller
> 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.
Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller
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
