My bad. For the future: we use gc for the go compiler, and GC (capital
letters) for the
garbage collector. Sorry for the confusion.

Il giorno martedì 23 febbraio 2016 16:07:14 UTC+1, Viktor Kojouharov ha
Yes, that's how people tend to do these things. I thought it would be
clear that I'm not talking about the compiler, but the actual program,
since I was talking about the gc and the target device's free memory

On Tuesday, February 23, 2016 at 5:00:33 PM UTC+2, alb.do...@gmail.com
You usually develop and compile on your computer, so the
memory usage of the compiler shouldn't be a problem. You generate
the binary on your machine and the transfer it to the small device.

Il giorno martedì 23 febbraio 2016 15:44:26 UTC+1, Viktor Kojouharov ha
There's no info on this?

On Monday, February 22, 2016 at 9:29:45 AM UTC+2, Viktor Kojouharov

I'm looking at using go (gccgo 5.3) on a mips device that doesn't have
a lot of memory. It has roughly around 70MB of free memory right now. I've
read some ancient comments that this might be much less than what the gc
requires to run, let along do anything. And among other things, this app
would start a builtin http server and also have a permanent websocket
connection to another server.

You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 5 of 9 | next ›
Discussion Overview
groupgolang-nuts @
postedFeb 22, '16 at 7:29a
activeFeb 24, '16 at 2:31p



site design / logo © 2021 Grokbase