Re: [9fans] Go on Plan 9?

> I tried a bootstrapped version on my RPi but it fails with a > "fork/exec ... virtual memory allocation failed” error when I try to > compile anything. According to stats I have plenty of memory left > when it runs. I’m not sure what to make of it. Any idea if the port > is complete or if

Re: [9fans] Go on Plan 9?

> Skip, isn't the point here that being able to run go binaries > in Plan 9 on an arm machine is news to most Plan 9 users? Go seems a little outside the scope of a Plan 9 release and I think it would take a greater interest by the community to bring it in. I seem to recall that Quanstro's 9atom

Re: [9fans] Go on Plan 9?

> I tried a bootstrapped version on my RPi but it fails with a "fork/exec ... > virtual memory allocation failed” error when I try to compile anything. Go needs a lot of virtual memory - it won't even pass the installation test suite if you give it less than a gigabyte. That was the reason for

Re: [9fans] Go on Plan 9?

> I tried a bootstrapped version on my RPi but it fails with a "fork/exec ... > virtual memory allocation failed” error when I try to compile anything. Go needs a lot of virtual memory - it won't even pass the installation test suite if you give it less than a gigabyte. That was the reason for

Re: [9fans] Go on Plan 9?

> Next to try on Plan 9: build a linux/s390x binary and find a machine to run > it on :) I have certainly done that with linux/386 under Plan 9. It works like a charm, even if the compilation is a lot slower than doing it natively on the target machine (which I could eventually install Go on).

Re: [9fans] Go on Plan 9?

Thanks Richard for doing the go port to plan9/arm. I was going to start on that myself until I found out it was already done. :-) I didn’t realize that Go was so virtual memory hungry. I wonder why stats didn’t show me a large peak of memory consumption before the go compiler died? Perhaps it

Re: [9fans] Go on Plan 9?

> It won't need a swap file unless the program forces all that to be > allocated, which it shouldn't, If you want to get to the satisfying ALL TESTS PASSED message at the end of the go install+test process, you will need a swap file, even on a 1GB raspberry pi. Trust me.

Re: [9fans] Go on Plan 9?

> That's insane. Really. The designer(s) of the test suite had bigger systems in mind, so there's lots of stuff running concurrently.

Re: [9fans] Go on Plan 9?

On 13 April 2016 at 15:42, Charles Forsyth wrote: > On 13 April 2016 at 15:39, Richard Miller <9f...@hamnavoe.com> wrote: > >> If you want to get to the satisfying ALL TESTS PASSED message at the end >> of the go install+test process, you will need a swap file, >> > >

Re: [9fans] Go on Plan 9?

> I didn’t realize that Go was so virtual memory hungry. I wonder why stats > didn’t show me a large peak of memory consumption before the go compiler died? stats -m shows physical memory usage. Every go program starts by allocating a huge block of virtual space for its garbage-collected

Re: [9fans] Go on Plan 9?

On 13 April 2016 at 14:08, Chris McGee wrote: > I believe that my rpi only has the 512MB of RAM so I’ll add swap. It should be enough to increase the available virtual space by changing that #define. It won't need a swap file unless the program forces all that to be

Re: [9fans] Go on Plan 9?

On 13 April 2016 at 15:39, Richard Miller <9f...@hamnavoe.com> wrote: > If you want to get to the satisfying ALL TESTS PASSED message at the end > of the go install+test process, you will need a swap file, > That's insane. Really.

Re: [9fans] Go on Plan 9?

> If you want to get to the satisfying ALL TESTS PASSED message at the end > of the go install+test process, you will need a swap file, even on a > 1GB raspberry pi. Trust me. Sounds like a challenge, but I never quite wanted to know whether Plan 9 swap is or isn't broken. Still, how much swap

Re: [9fans] Go on Plan 9?

Ah, that makes sense. It’s virtual memory and not the physical memory. Do you think that your changes to the bcm will make it to 9front? If not, any chance I could have the diffs so that I can try merging them in there myself? Thanks, Chris

Re: [9fans] Go on Plan 9?

I tried that at some point. Got pi2 booting with one core, crashed with multiple, but then again, I'm new to having to be that intimate with assembly and kernel mode. I'd suggest trying from scratch to port things, but there are a few 9front differences that make it much more than just a diff.

Re: [9fans] Go on Plan 9?

> Still, how much swap are we talking about? On a 1GB system, the default test suite swaps in only a handful of places. It's possible to limit the concurrency enough to cut out swapping, but then it takes longer because there's less opportunity to overlap cpu-bound tests with file I/O and

Re: [9fans] Go on Plan 9?

I use GOROOT=$home/go to keep up with tip. after bootstrapping, rebuild the standard packages and commands: % GOBIN=$home/bin/386 $home/go/bin/go install -a std cmd and % GOARCH=arm go install -a std cmd then in my profile: % test -d $home/go/bin/plan9_^$cputype && bind -a