HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
llvm
llvm-project
LLVM2019–2026
llvm / llvm-project

llvm-project

The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.

Languages & Compilers
Explore on GitHubRead Hacker News discussions
203Distinct people
323Mentions
0Explicit recommenders
41.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.

GitHub

Where it is used

No documented product use was verified in the last source check.

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

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 4:01:40 AM 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 year323 dated mentions

Observed mentions: 2019-03-20 14:14:12 UTC to 2026-10-31 13:03:47 UTC.

0204060801002019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 21 mentions; 5 submissions, 16 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 29 mentions; 4 submissions, 25 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 34 mentions; 7 submissions, 27 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 38 mentions; 1 submissions, 37 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 55 mentions; 5 submissions, 50 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 100 mentions; 6 submissions, 94 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 38 mentions; 2 submissions, 36 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC808
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC21516
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC29425
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC34727
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC38137
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC55550
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC100694
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC38236

What Hacker News says

8 sources
riscy·Sep 19, 2019
Doesn't the "LLVM Exceptions" part of the license take care of the patent issue you mention? "[...] if a court of competent jurisdiction determines that the patent provision (Section 3), [...] conflicts with the conditions of the GPLv2, you may retroactively and prospectively choose to deem waived or otherwise exclude such Section(s) of the License [...]" Source: https://github.com/llvm/llvm-project/blob/master/llvm/LICENS...
In LLVM 9.0
brynet·Sep 19, 2019
Note that this release (9.x) marks the first to be no longer available under the original permissive NCSA (BSD-like) LLVM license, going forward the LLVM project has moved to an "Apache 2.0 with LLVM Exceptions" for everything. And not just the compiler itself, but also sub-projects like the supporting libc++/libc++abi standard libraries. This change only happened due to corporate pressure, and was done without considering the larger impact towards the open source community. This will undoubtedly effect many projects and companies alike going forward, but notably the OpenBSD project can no longer merge in new changes, which will ship with 8.0.1 later this year in 6.6. The Apache 2.0 license is not considered permissive enough to be included in the base system of OpenBSD, it muddies the line between Copyright law and US Contract law; addin
Read the rest
g additional restrictions related to patents that may terminate rights. https://lists.llvm.org/pipermail/llvm-dev/2017-April/112300.... https://www.openbsd.org/policy.html It is very unfortunate that the LLVM project has ignored the concerns expressed by developers of an open source operating system project that have been eagerly adopting a clang based toolchain, across many platforms (arm64/armv7/i386/amd64/octeon/..) by default, and has been working on new innovative security mitigations (RETGUARD, ROPGadgetFixup framework, register allocator rearranging) along the way. I will take this opportunity to ask, if you're a current LLVM developer/contributor, please consider making your changes also available under the terms of the original permissive license. For example, explicitly stating publically as such when mailing patchsets or pull requests. This would save having to privately ask permission to backport changes on case-by-case basis. https://github.com/llvm/llvm-project/blob/release/8.x/clang/...
In LLVM 9.0
lpage·Sep 19, 2019
> "Support for asm goto, enabling for example the mainline Linux kernel for x86_64 to build with Clang" This is big. Support for asm goto was merged into the mainline earlier this year, but now it's released [1]. Aside from the obvious implications of this - being able to build the kernel with LLVM - working with eBPF/XDP just got way easier [2]. [1] https://github.com/llvm/llvm-project/commit/784929d0454c4df6... [2] https://www.spinics.net/lists/netdev/msg544057.html
In LLVM 9.0
Joky·Apr 12, 2019
LLVM supports old platforms: some CI bots are targeting stable Debian, or Ubuntu 14.04. LLVM is currently moving to C++14, which is a pain for some users like TensorFlow for instance which supports Ubuntu 14.04: the c++ standard library is too old. There are technical solutions for everything but for a component like LLVM, not pressuring its users into convoluted workflow is important. Of course the LLVM developpers would love to just use the latest version of the standard all the time. For the library part of the standard, it is worked around by having its own: https://github.com/llvm/llvm-project/blob/master/llvm/includ... (and others in the same directory)
In F18 Fortran compiler and runtime project is accepted as part of LLVM project
slacka·Mar 20, 2019
There truly is nothing to it. I just built it for the first time on this fresh install of Ubuntu. You can just copy and paste the lines from the getting started page.[1] Here's my .bash_history: $ git clone https://github.com/llvm/llvm-project.git $ cd llvm-project $ mkdir build && cd build $ cmake -DLLVM_ENABLE_PROJECTS=clang -DCMAKE_BUILD_TYPE=Release -G "Unix Makefiles" ../llvm $ make -j4 Took < 40 min on an old laptop. [1] https://clang.llvm.org/get_started.html
In LLVM 8.0.0 Release

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.