4 ms·
> I wonder if there are any estimates on how close to the original performance they think they can get. Do they expect to reach parity by, say, 1.6 or will it a
by chimeracoder 11y ago
> I wonder if there are any estimates on how close to the original performance they think they can get. Do they expect to reach parity by, say, 1.6 or will it always be slower?
I imagine that's just a side-effect of rewriting the entire compiler; I'd expect the next versions to improve on the speed.
Though in the meantime, if compilation time is an issue, you can always try gccgo. On my larger projects, it's slightly faster than gc 1.5. YMMV, obviously.
- gillianseed 11y agoWhat's the performance in gccgo nowadays, back when I tried it certain things was slightly faster but a lot was slower compared to the official compiler. I read that it mainly had to do with lack of escape analysis, has this changed in recent gcco releases ?
- Zariel 11y agoThe new compiler is now garbage collected, and is generating lots of garbage, when the old compiler ran without any garbage collection. There is an interesting thread from the mailing list about this [0] [0] https://groups.google.com/d/topic/golang-dev/6obxRcm-rqc/discussion https://groups.google.com/d/topic/golang-dev/6obxRcm-rqc/dis...