Golang dev.ssa branch merged into tip
github.com
Golang dev.ssa branch merged into tip
1–10 of 37 posts
Re: Golang dev.ssa branch merged into tip
#2So... not been closely following development on Go. What does this mean?
Re: Golang dev.ssa branch merged into tip
#3So... not been closely following development on Go. What does this mean?
Just a guess: it's probably static single assignment for the IR.
https://www.cs.cmu.edu/~fp/courses/15411-f08/lectures/09-ssa...
Re: Golang dev.ssa branch merged into tip
#4So... not been closely following development on Go. What does this mean?
Just a guess: it's probably static single assignment for the IR. https://www.cs.cmu.edu/~fp/courses/15411-f08/lectures/09-ssa...
It appears it's a new way to do code generation. So any adding of new architectures is dead in the water until this is resolved.
https://groups.google.com/forum/#!topic/golang-dev/zz-gWGXFZ...
Re: Golang dev.ssa branch merged into tip
#5So... not been closely following development on Go. What does this mean?
It is the new backend for the Go Compiler
See: https://docs.google.com/document/d/1szwabPJJc4J-igUZU4ZKprOr...
Re: Golang dev.ssa branch merged into tip
#6Earlier quoted context omitted.
Just a guess: it's probably static single assignment for the IR. https://www.cs.cmu.edu/~fp/courses/15411-f08/lectures/09-ssa...
It appears it's a new way to do code generation. So any adding of new architectures is dead in the water until this is resolved. https://groups.google.com/forum/#!topic/golang-dev/zz-gWGXFZ...
Actually, the opposite. The merging of the branch means that people are now free to continue work on adding new architectures.
Re: Golang dev.ssa branch merged into tip
#7Earlier quoted context omitted.
It appears it's a new way to do code generation. So any adding of new architectures is dead in the water until this is resolved. https://groups.google.com/forum/#!topic/golang-dev/zz-gWGXFZ...
Actually, the opposite. The merging of the branch means that people are now free to continue work on adding new architectures.
Did the compiler get even slower on tip? I know that was a concern with this change
Re: Golang dev.ssa branch merged into tip
#8Earlier quoted context omitted.
Actually, the opposite. The merging of the branch means that people are now free to continue work on adding new architectures.
Did the compiler get even slower on tip? I know that was a concern with this change
10% slower, which isn't too bad, let's hope they can now focus on improving compilation speed, I miss go 1.4 having recently upgraded. It would be really nice to see that actually improve for 1.7 instead of regressing.
Re: Golang dev.ssa branch merged into tip
#9So... not been closely following development on Go. What does this mean?
Improved optimizations which will also be easier to implement, with the result being faster and also typically smaller code.
Re: Golang dev.ssa branch merged into tip
#10Earlier quoted context omitted.
Just a guess: it's probably static single assignment for the IR. https://www.cs.cmu.edu/~fp/courses/15411-f08/lectures/09-ssa...
It appears it's a new way to do code generation. So any adding of new architectures is dead in the water until this is resolved. https://groups.google.com/forum/#!topic/golang-dev/zz-gWGXFZ...
SSA, once you understand it, is easier to work with than almost all other forms of instruction sets. I'd argue that it would only accelerate new architecture in the long-run.
I'm interested in why LLVM was disqualified. Was it simply never considered or is it incompatible with the Go type system, calling convention, etc.?