3 ms·
Thanks much appreciated!! Go's syscall interface looks clean so it wouldn't be too much to deal with either way. I'd be happy with put+get char to start with!
by eckyptang 14y ago
Thanks much appreciated!! Go's syscall interface looks clean so it wouldn't be too much to deal with either way. I'd be happy with put+get char to start with!
I don't mind writing a new backend as the compilers are quite easy to work with by the looks. Plus it'll exercise my brain more than typical CRUD apps.
- 4ad 14y agoThe C compiler in the Go tree that's used to compile the C bits of the runtime already supports ARMv4 (unsurprisingly, since it was written a long time ago for Plan 9 and Inferno), only the Go compiler would need modifications. The compiler suite is a pleasure to work on, really clear code, just like all the other code Ken Thompson wrote. Good luck.
- eckyptang 14y agoEven nicer. Thanks for the info. I'll submit results if I get anywhere - might take a month or two :-) Currently trying to a (any) toolchain online first to test the board and get a ucLinux kernel up (gcc cross-compiler + OpenOCD + Olimex ARM-JTAG + ThinkPad Ultrabay parallel port stack should be 'fun').
- eckyptang 14y agoReplying to myself. ucLinux + hello world + gdb via OpenOCD online at 4AM :) Now for the go toolchain...