News for hackers. Stuff that matters.
Re:Go 1.3 beta 1 released by jshen on Tuesday April 22, 2014 @11:47PM (#7631966)
Random question, why would someone use gccgo over the standard go compiler?
Re:Go 1.3 beta 1 released by cespare on Tuesday April 22, 2014 @11:58PM (#7632007)
One reason is that gccgo supports many architectures that gc does not (SPARC, MIPS, PowerPC, Alpha). It also was the only way to get Go on Solaris until the more recent port of gc to that platform.

gccgo is also supposed to produce better code for certain computationally heavy workloads.

Re:Go 1.3 beta 1 released by 4ad on Wednesday April 23, 2014 @06:30AM (#7633127)
> gccgo is also supposed to produce better code for certain computationally heavy workloads.

Unfortunately, this is very seldom true. Gccgo could potentially generate faster floating point code, but its lack of escape analysis grinds it to a halt.

Re:Go 1.3 beta 1 released by whyrusleeping on Wednesday April 23, 2014 @01:02AM (#7632201)
with gccgo you get to take advantage of a lot of gcc's optimizations (-O3) and it can generate faster code because of it.
Re:Go 1.3 beta 1 released by 4ad on Wednesday April 23, 2014 @06:28AM (#7633118)
There is extremely little code in the world that is faster with gccgo. Yes, gccgo can do better with floating point, but the lack of escape analysis slows it down tremendously in every real world situation out there.

http://dave.cheney.net/2013/11/19/benchmarking-go-1-2rc5-vs-...

Re:Go 1.3 beta 1 released by supersillyus on Wednesday April 23, 2014 @11:07AM (#7634385)
There is a GSOC to add escape analysis (https://www.google-melange.com/gsoc/project/details/google/g...). It'll be interesting to see how that affects things.
Re:Go 1.3 beta 1 released by whyrusleeping on Wednesday April 23, 2014 @01:36PM (#7635518)
Wow. I guess the last time i look at the differences was around 1.1 Thanks for the correction