GopherCon 2016: The Design of the Go Assembler - Rob Pike

Channel:Gopher Academy · Length:23:56 · Published:2016-08-18 · Views:115926

Watch on YouTube

Summary

Rob Pike's GopherCon 2016 talk on the design of the Go assembler, explaining why Go uses a common assembly language translated to each architecture.

Why HN recommends it

HN points to it for background on how the Go toolchain targets many architectures and why its assembler is designed that way.

Its Rob Pike talking about the go assembler and he answers a few of your questions. — HN, 2017

C, C++, Rust, Go & systems languages · Compilers, interpreters & program analysis

Subtitles (excerpt)

thank you that's the most enthusiastic and largest response for a talk about Assembly Language in many years you might wonder uh why we're talking about the assembler um and there's a reason but I'm going to come to it um first of all you might ask why do we care about Assembly Language at all so let's go back to 1970 for a quote from an IBM manual which reads the most important single thing to realize about assembler language is that it enables the programmer to use all system 360 machine functions as if he were coding in system 360 machine language now there's a lot of sort of dated aspects of that but the fundamental point is Right assembler is how you talk to the machine at the very lowest level and in fact even today we still need Assembly Language it used to be that all you had was assembler and then what we called highlevel languages like Fortran and Cobalt came along um and sort over time but slowly displac them um and even C for a while was argued as being you know a highle language when when you had assembler available but we still need assembler today because of this access that provides the machine you needed to bootstrap your environment uh to get the stacks running do switching between contexts in the go

On Hacker News

This is relevant [VIDEO] Its Rob Pike talking about the go assembler and he answers a few of your questions. — fourseventy, 2017-09
Here's a good talk about the Go assembler backend: [VIDEO] Spoiler: they're nearly to the point (maybe now they've achieved it fully) of autogenerating a new language backend from ISA documentation PDFs! Bring that up next time someone complains about Go not using LLVM. — bkeroack, 2017-04
Have you looked at the Go toolchain at all? I don't know much about it, but they implemented their back ends in a manner that is much smaller than LLVM and GCC. And it sounds like the architecture of the compiler is significantly different. I watched this talk and it was pretty interesting: [VIDEO] [LINK] If I am understanding right, the claim is that they have a single assembly language for ALL … — chubot, 2017-02
I'm reminded of a 2016 [talk][1] where Rob Pike describes the common-denominator assembly language that the Go compiler generates. Then that assembly is translated into machine-specific code via table lookups. See the 11 minute mark. [1]: [VIDEO] — MathMonkeyMan, 2025-04
> Overall, pretty weird stuff. I am not sure why the Go team went down this route. Maybe it simplifies the compiler by having this bespoke assembly format? Rob Pike spoke on the design of Go's assembler at a talk in 2016 [1][2]. I think it basically came down to the observation that most assembly language is roughly the same, so why not build a common assembly language that "lets you talk to the … — saclark11, 2024-10

Related videos