Go builds on Plan9 suffer from the post-1.9 performance regression.
> On Sep 19, 2019, at 10:29 PM, Steve Simon <[email protected]> wrote:
>
> hi,
>
> my plan was to build and run/debug go on a raspberry pi 4 running plan9, not
> to cross compile.
>
> i am confident in the linux cross compile environment i was just concerned
> about the plan9 os/runtime support for the pi.
>
> i guess it comes down to plan9 os interface for the arm.
>
> people said it is painful, you mean the pi is slow?
>
> thanks for the help.
>
> -Steve
>
>> On 20 Sep 2019, at 5:37 am, Lyndon Nerenberg <[email protected]> wrote:
>>
>> Matthew Veety writes:
>>
>>> Building anything on a raspberry pi is a bit of a chore. I highly=20
>>> recommend running go on your cpu server and/or local to your filesystem.=20
>>> The generated binaries seem to work fine.
>>
>> Go does wonderfully when it comes to generating binaries for
>> non-native architectures. I have a few Go-based tools I use at
>> work that I build on any number of archictures (macos, freebsd,
>> openbsd, linux / armX, i386, amd64)) that I need to run on one or
>> many of the above. They all just work. Makes debugging a breeze.
>>
>> But now that they are succumbing to the shared lib/obj doctrine, I'm sure
>> I will soon go back to writing C code, since the advantage of those
>> static go binaries is about to be lost :-(
>
>
