HUhu3·Sep 27, 2024
Go's backend is custom.
They consider LLVM too slow and made their own.
https://github.com/go-llvm/llgo is third party and archived.
In Register Allocation in the Go Compilergo-llvm
llgo
Go2014–2024
go-llvm / llgo · Archived
llgo
LLVM-based compiler for Go
7Distinct people
7Mentions
0Explicit recommenders
1.3KGitHub stars
What to know before exploring
What it is
LLVM-based compiler for Go
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year7 dated mentions
Observed mentions: 2014-07-04 07:05:38 UTC to 2024-09-27 13:50:47 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
7 sources> And of course, today there is an LLVM-hosted compiler for Go, and many others, as there should be.
Isn't that the dead llgo effort?
https://github.com/go-llvm/llgo (now archived)
Its readme points to a dead link on the LLVM website, and it looks like there's no matching Go project under the LLVM org.
Does anyone know if there really is still a working LLVM based Go toolchain (other than TinyGo)?
In Go: What we got right, what we got wrongThe official compiler doesn't. Then there's llgo [0] and gollvm [1].
[0] https://github.com/go-llvm/llgo
[1] https://go.googlesource.com/gollvm/
In A Farewell to GoFWIW this used to be hosted on GitHub here: https://github.com/go-llvm/llgo
Not really obvious to me how much progress has been made since the transition to LLVM repo.. but last time I checked it was missing _a lot_:
- No garbage collector
- No escape analysis
- etc.
In Llgo – A Go frontend for LLVM, written in Gollgo is already a thing: https://github.com/go-llvm/llgo
In New SSA Back End for the Go CompilerGo can already leverage some of gcc's optimizations. There's also https://github.com/go-llvm/llgo
In Swift and Go: Building a Fast Future> I'm not so excited about Go, I honestly find Rust better.
Same here, but Go has productive libraries that can help you hit the ground running. Just with the packaged standard libraries, you can do things like have a useful webserver going. I prefer Rust though and might stick with JS until I exhaust it .. or until Rust matures enough to put into production and then jump fully on to Rust. Rust compiles to llvm-bitcode, unlike Go, so that's a win for me.
edit: I stand corrected - https://github.com/go-llvm/llgo
In Farewell Node.js