> > My primary question is whether I should transform ssa.Value into another > type that allows SSA transformation (register renaming etc.) or if > there's a chance the x/tools/go/ssa package will be extended to allow > this. > The x/tools/go/ssa package exists to do static analysis, so SSA transformation is not required.
There is SSA transformation code in the go project, but it is for a different, internal, SSA form which is used for the amd64 backend of the go 1.7 compiler. Personally, having both generated code from the x/tools/go/ssa SSA form (http://tardisgo.github.io/) and played with improving the interpreter (https://github.com/go-interpreter/ssainterp), I hope the project will eventually have a public SSA form that has some built-in transformation optimization passes and can be transformed further by keen enthusiasts. That could unleash a wave of further innovation that would only help the go language. If you have the energy and enthusiasm to create that, in parallel to the compiler's internal SSA form, I wish you well. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
