Issue #56474 added support for instruction alignment on the amd64 architecture. This is achieved with the PCALIGN assembly pseudo instruction, which inserts NOP's to align to a given boundary. ...

I want to run a go binary on an ARMv7 target that doesn't have a hardware floating point unit (FPU). (The ARMv7 specification does not require a hardware FPU; it is optional.) Currently, the on...

TLDR: not gonna happen soon, sorry

Status update
A few people who stand behind Go-perf are on low power now and 1 person cannot organise everything and be happy with the quality of the event. So, after some discussion that should happened earlier, w...

Problem The default setting of runtime.GOMAXPROCS() (to be the number of os-apparent processors) can be greatly misaligned with container cpu quota (e.g. as implemented through cfs bandwidth contro...

Google's Go compiler and runtime team meets periodically (roughly weekly) to discuss ongoing development of the compiler and runtime. While not open to the public, there's been desire by th...

I’m going to show you how I took a very simple program and made it run almost 5 times faster, with very minimal adjustments. You may know…

Proposal: unique package Updated: 10 April 2024 Oct 4th EDIT: Changed package name from "intern" to "unique" and renamed "Symbol" to "Handle" based on feedba...

Analyzing how Go decides what escapes to the heap, and how to visualize it in VSCode.

There are 2X AES throughput improvements available here #42726. However the assembly implementations are too big: https://go-review.googlesource.com/c/go/+/286852/comments/1b1a6e65_4e27a3f8 From th...

GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects.

Fourteen years after the launch of Go, there is much to think about. With the benefit of hindsight, this talk explores some of the lessons learned from Go's progress so far: not just the things that went well but also the things that could have been done…