News for hackers. Stuff that matters.
Re:Rust Priorities after 1.0 by rdtsc on Thursday April 16, 2015 @11:13PM (#9392076)
> Go performance is going to converge on C performance with new optimization's being written after go 1.5.

Do you have more details. It would seem like it would be rather difficult to do that. Sure it can rival Java in some workloads, but C performance is a tall claim.

Re:Rust Priorities after 1.0 by andrewchambers on Thursday April 16, 2015 @11:32PM (#9392118)
Go is currently pretty fast, maybe half as fast as C. There is a new backend for the Go compiler being planned which uses more modern techniques.

This plan[1] estimates at 10 percent speed improvements initially, I just think they will continue to progress further over time once the SSA framework is built. They will be able to port essentially every optimization llvm uses eventually, and add a few new ones that can rely on memory safety and pointer aliasing guarantees Go provides.

Go can also do whole program analysis with the ssa form because all source is present at build time.

An addition of a moving garbage collector may also improve cache locality. We will see, google cares about making servers efficient, as it saves money in power.

[1] https://docs.google.com/document/d/1szwabPJJc4J-igUZU4ZKprOr...

Re:Rust Priorities after 1.0 by sinistersnare on Friday April 17, 2015 @02:54AM (#9392599)
What guarantees does Go provide about pointer aliasing? I have no production code in Go, but from what I have played with, Go has no way of indicating that a pointer is not aliased, so how can it optimize that, other than through static analysis, which will not catch the majority of cases.

I ctrl-f'd "alias" on your paper that you linked, and no mention is shown.

edit: in fact, I forgot to look for "escape analysis." So it does get mentioned, but only to point out that it is a non-goal of the project.

Re:Rust Priorities after 1.0 by andrewchambers on Friday April 17, 2015 @08:40PM (#9397919)
Go just guarantees different typed pointers don't alias, I think C has a flag to allow this assumption though.
Re:Rust Priorities after 1.0 by rdtsc on Friday April 17, 2015 @12:03AM (#9392200)
That makes sense Andrew, thanks for explaining.