On Sat, 2015-08-22 at 11:06 +0000, Laeeth Isharc via Digitalmars-d -learn wrote: > […] > > Builds in Go 1.5 will be slower by a factor of about two. The > automatic translation of the compiler and linker from C to Go > resulted in unidiomatic Go code that performs poorly compared to > well-written Go. Analysis tools and refactoring helped to improve > the code, but much remains to be done. Further profiling and > optimization will continue in Go 1.6 and future releases. For > more details, see these slides and associated video. >
This is about compiler performance, not about generated code performance. Anyone interested in performance with Go currently uses gccgo: the standard Go compiler does not generate particularly well optimized code. This has been a resourcing choice to date, it is not a failing. gccgo on the other hand makes use of the whole GCC optimization chain. On the other hand gc is blindingly fast at compilation compared to gccgo. This seems reminiscent of dmd vs. ldc and gdc! -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Road m: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
