I hope to work on making much of the SSA backend compilation
concurrent. This would involve some significant refactoring, so I
would wait for the typealias and inline branches to get merged. That
*might* also include adding tracing to go commands (issue 15736, in
part out of concern about issue 17969), which would wait for Russ's
cmd/go work. Russ, will you give an all-clear here when that work is
I also have a handful of minor compiler optimizations
(performance+toolspeed) queued. Keith, I'm happy to get your batch of
changes landed before mine. Please let me know when your CL backlog is
Keith, which areas of compiler toolspeed do you plan to look at? In
the unlikely event that I have extra time, I hope to look at
regalloc/liveness performance and moving common sources of dead blocks
from walk to ssa (e.g. switch statements).
>> For more options, visit https://groups.google.com/d/optout.
> You received this message because you are subscribed to the Google Groups
> "golang-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
Unfortunately I do not remember the person's name by heart. But I remember vividly this person also contributed with many examples, so o hope to not be alone this time.
I should like also to get from the current team some feedback on how to approach package owners/main contributors. As the coverage improves, it also gets more complicated to create meaningful examples that doesn't just repeat somehow what is one the tests (for the obvious reason that I do not know everything).
Any suggestion is welcome. And I shall try hard to disturb as few people as necessary with questions about developing examples.
Also, we're trying something new this cycle:A bunch of the Google employees who normally only work on Google-internal libraries will be spending a week (Mon Feb 6th - Fri Feb 10th) working in the open source world, working on bugs/features/performance or whatever else that scratches their itch or they find entertaining. So you'll probably all see some new names. Please help out newcomers if they're confused about the process or tooling. Of course, this isn't an event exclusive to Googlers. If you or your organization also wants to concentrate their attention on bugs & the Go libraries that week, the more the merrier! More docs on that process later.
ARM64 disassembler for supporting basic instructions (I mean all instructions supported by current Go assembler) can be ready before May. We can submit the basic support first to align to your development cycle.
After that, we will continue improving the disassembler for supporting ARM64 advanced SIMD instructions so that we can make optimizations based on these vector instructions later.
I’d like to update ARM64 decoder development progress: we have finished the decoder table (1210 items) for all ARM64 instructions and all base instructions have pass the GNU syntax test which compares output with external objdump.
But we encounter a new problem: Go assembly is not well defined for ARM64 and I have started a new thread about the topic: https://groups.google.com/forum/#!topic/golang-dev/rWgDxCrL4GU
Since our final aim is to use decoder to verify ARM64 assembler, I’d like to make some changes to assembler for better supporting ARM64 before finishing the remaining work of decoder, especially GoSyntax (plan9x.go).
We expect to finish ARM64 decoder before the end of May.
From: Brad Fitzpatrick [mailto:brad...@golang.org]
Sent: Thursday, February 23, 2017 9:53 AM
To: Wei Xiao
Subject: Re: [golang-dev] Re: Go 1.9 planning & kick-off week
The three new-code development months for Go 1.9 are February, March, and April. The 3 stabilization months are May, June, July.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
You received this message because you are subscribed to the Google Groups "golang-dev" group.
Yes, i will push ARM64 disassembler to x/arch.I plan to add some changes and bug fixings to the assembler this week and left the remaining refinement work later.Btw, when will the window open again for accepting changes to assembler after April?
I submitted the patch (https://go-review.googlesource.com/c/43651/) three weeks ago but get no feedbacks so far.