Re: [9fans] go under plan9 on the radpberry pi?

[Richard Miller]

> Only lightly tested.

In a sense, plan9/arm go is tested as well as any other platform:
under the go continuous development process, every time a change
is made to the compiler or runtime library, a complete test suite
is run on builder machines for every supported architecture and
operating system.  If you look at https://build.golang.org and
scroll wa over to the right, the plan9/arm column refers
to a set of Raspberry Pi machines run by David du Columbier and me.

In another sense, it's probably not very well tested at all:
I'm not aware of any production application being run on go in
Plan 9, on any machine architecture.  I haven't used go seriously
myself, but I find the test suite gives the OS such a brutal workout
(especially with small physical memory) that it's a good way
to flush out underlying Plan 9 bugs.

The tests show some intermittent hard-to-reproduce failures ("flakes")
on all the Plan 9 builders.  Many are timing issues because the tests
make assumptions about absolute speed of builder machines; but there
are some "can't happen" panics during garbage collection which smell
like a cache or memory barrier problem.  Please don't use plan9/arm
go to run your nuclear power plant just yet ...

Re: [9fans] go under plan9 on the radpberry pi?

[Richard Miller]

> If you mean the go compiler itself, hopefully the 2GB VM you
> get on 9p/pi4 is enough to compile the compiler using a
> cross-compiled bootstrap compiler.

The compiler can compile itself natively on a pi2 or pi3.
No need to activate swap space, unless you want to run the
full test suite.

> Another option worth exploring may
> be AOE as pi4 has a GbE (I haven't tried this yet).

My go test builders are running with "local" fossil on a slice
of disk provided over AoE from an atom server.  I tried various
configurations and this gave me the best performance.  This is
with 3B+ machines on "gigabit" ethernet throttled by rubbish usb.

Pi4 has proper GbE, but also has usb3 so a local ssd drive might
be a practical alternative.  More experiments to do.

Re: [9fans] go under plan9 on the radpberry pi?

[Steve Simon]

hi,

thanks richard, this is perfect

i could not have asked for more.

-Steve


On 20 Sep 2019, at 9:43 am, Richard Miller <9f...@hamnavoe.com> wrote:

>> Only lightly tested.
> 
> In a sense, plan9/arm go is tested as well as any other platform:
> under the go continuous development process, every time a change
> is made to the compiler or runtime library, a complete test suite
> is run on builder machines for every supported architecture and
> operating system.  If you look at https://build.golang.org and
> scroll wa over to the right, the plan9/arm column refers
> to a set of Raspberry Pi machines run by David du Columbier and me.
> 
> In another sense, it's probably not very well tested at all:
> I'm not aware of any production application being run on go in
> Plan 9, on any machine architecture.  I haven't used go seriously
> myself, but I find the test suite gives the OS such a brutal workout
> (especially with small physical memory) that it's a good way
> to flush out underlying Plan 9 bugs.
> 
> The tests show some intermittent hard-to-reproduce failures ("flakes")
> on all the Plan 9 builders.  Many are timing issues because the tests
> make assumptions about absolute speed of builder machines; but there
> are some "can't happen" panics during garbage collection which smell
> like a cache or memory barrier problem.  Please don't use plan9/arm
> go to run your nuclear power plant just yet ...
> 

[9fans] building Alef language

[Phil Kulin]

I try to build Alef language
latest 9front iso

%9fs 9pio
# I don't know why, but "tar x alef.tgz" command do nothing...
%tarfs /n/sources/extra/alef.tgz
%dircp /n/tapefs/sys /sys
% cd /sys/src/alef
% mk all
mk $objtype.all
@{cd v; mk all }
@{cd k; mk all }
@{cd 8; mk all }
@{cd lib; mk all }
yacc -d ../port/parl.y

conflicts: 2 shift/reduce
mv y.tab.h ../port/y.tab.h
8c -w -I../port cinit.c
8c -w -I../port code.c
machdep.h:329 ../port/parl.h:332 cinit.c:6 syntax error, last name: Fconv
mk: 8c -w -I../port cinit.c  : exit status=rc 40921: 8c 40925: error
machdep.h:329 ../port/parl.h:332 code.c:6 syntax error, last name: Fconv
mk: @{cd v; mk ...  : exit status=rc 40909: rc 40911: mk 40912: error
mk: mk $objtype.all  : exit status=rc 40906: mk 40908: error
%

I think that problem in "Fconv" definition...

-- 
Non nobis Domine non nobis sed Nomini Tuo da gloriam
Phil Kulin

Re: [9fans] building Alef language

[Rodrigo G . López]

somebody please summon The BurnZeZ.


-rodri

On Fri, Sep 20, 2019, 10:46 PM Phil Kulin  wrote:

> I try to build Alef language
> latest 9front iso
>
> %9fs 9pio
> # I don't know why, but "tar x alef.tgz" command do nothing...
> %tarfs /n/sources/extra/alef.tgz
> %dircp /n/tapefs/sys /sys
> % cd /sys/src/alef
> % mk all
> mk $objtype.all
> @{cd v; mk all }
> @{cd k; mk all }
> @{cd 8; mk all }
> @{cd lib; mk all }
> yacc -d ../port/parl.y
>
> conflicts: 2 shift/reduce
> mv y.tab.h ../port/y.tab.h
> 8c -w -I../port cinit.c
> 8c -w -I../port code.c
> machdep.h:329 ../port/parl.h:332 cinit.c:6 syntax error, last name: Fconv
> mk: 8c -w -I../port cinit.c  : exit status=rc 40921: 8c 40925: error
> machdep.h:329 ../port/parl.h:332 code.c:6 syntax error, last name: Fconv
> mk: @{cd v; mk ...  : exit status=rc 40909: rc 40911: mk 40912: error
> mk: mk $objtype.all  : exit status=rc 40906: mk 40908: error
> %
>
> I think that problem in "Fconv" definition...
>
> --
> Non nobis Domine non nobis sed Nomini Tuo da gloriam
> Phil Kulin
>
>

Re: [9fans] go under plan9 on the radpberry pi?

[Bakul Shah]

On Fri, 20 Sep 2019 09:53:07 +0100 Richard Miller <9f...@hamnavoe.com> wrote:
>
> > Another option worth exploring may
> > be AOE as pi4 has a GbE (I haven't tried this yet).
>
> My go test builders are running with "local" fossil on a slice
> of disk provided over AoE from an atom server.  I tried various
> configurations and this gave me the best performance.  This is
> with 3B+ machines on "gigabit" ethernet throttled by rubbish usb.
>
> Pi4 has proper GbE, but also has usb3 so a local ssd drive might
> be a practical alternative.  More experiments to do.

On linux/pi4 I get about 230MB/s for seq. read on a $10 USB3.1
Samsung flash drive. Time to get a new SSD!

Re: [9fans] building Alef language

[Sean Hinchee]

As rodri states BurnZeZ has a copy of Alef he got building and kind of 
running under 9front/386. I kind of got the same thing at one point, but 
his is way better :)


I know a snapshot of it is on mycroftiv's public grid around 
/n/griddisk/burnzez


I don't know if he has a public version-controlled copy.

Cheers,
Sean

On 9/20/19 2:05 PM, Rodrigo G. López wrote:

somebody please summon The BurnZeZ.


-rodri

On Fri, Sep 20, 2019, 10:46 PM Phil Kulin > wrote:


I try to build Alef language
latest 9front iso

%9fs 9pio
# I don't know why, but "tar x alef.tgz" command do nothing...
%tarfs /n/sources/extra/alef.tgz
%dircp /n/tapefs/sys /sys
% cd /sys/src/alef
% mk all
mk $objtype.all
@{cd v; mk all }
@{cd k; mk all }
@{cd 8; mk all }
@{cd lib; mk all }
yacc -d ../port/parl.y

conflicts: 2 shift/reduce
mv y.tab.h ../port/y.tab.h
8c -w -I../port cinit.c
8c -w -I../port code.c
machdep.h:329 ../port/parl.h:332 cinit.c:6 syntax error, last name:
Fconv
mk: 8c -w -I../port cinit.c  : exit status=rc 40921: 8c 40925: error
machdep.h:329 ../port/parl.h:332 code.c:6 syntax error, last name: Fconv
mk: @{cd v; mk ...  : exit status=rc 40909: rc 40911: mk 40912: error
mk: mk $objtype.all  : exit status=rc 40906: mk 40908: error
%

I think that problem in "Fconv" definition...

-- 
Non nobis Domine non nobis sed Nomini Tuo da gloriam

Phil Kulin

Re: [9fans] building Alef language

[Lucio De Re]

I have a version for legacy Plan 9, lightly tested, that I have not
looked at in ages.

Happy to haul it out, but I see little value in it. Go may have
idiosyncrasies, but it is much more suited to modern architectures.
That said, had Go not surfaced, I would have much preferred Alef to
many other options.

Don't forget the rationale for dropping Alef: support for the
language, across many architectures and including many libraries would
have been crippling.

Both of those are now Go's strong suits.

Lucio.

PS: A tar archive may be on sources under "proxima" - it's been a long time.