HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
exo-lang
exo
Python2025–2025
exo-lang / exo

exo

Exocompilation for productive programming of hardware accelerators

5Distinct people
5Mentions
0Explicit recommenders
747GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Exocompilation for productive programming of hardware accelerators

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 3-hour interval5 dated mentions

Observed mentions: 2025-03-13 22:22:55 UTC to 2025-03-16 17:12:05 UTC.

0122025-03-13 21:00:00 UTC to 2025-03-14 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 13, 21:002025-03-14 00:00:00 UTC to 2025-03-14 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-14 03:00:00 UTC to 2025-03-14 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-14 06:00:00 UTC to 2025-03-14 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-14 09:00:00 UTC to 2025-03-14 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-14 12:00:00 UTC to 2025-03-14 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-14 15:00:00 UTC to 2025-03-14 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-14 18:00:00 UTC to 2025-03-14 21:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025-03-14 21:00:00 UTC to 2025-03-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-15 00:00:00 UTC to 2025-03-15 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-15 03:00:00 UTC to 2025-03-15 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-15 06:00:00 UTC to 2025-03-15 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 15, 06:002025-03-15 09:00:00 UTC to 2025-03-15 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-15 12:00:00 UTC to 2025-03-15 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-15 15:00:00 UTC to 2025-03-15 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-15 18:00:00 UTC to 2025-03-15 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-15 21:00:00 UTC to 2025-03-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-16 00:00:00 UTC to 2025-03-16 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-16 03:00:00 UTC to 2025-03-16 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-03-16 06:00:00 UTC to 2025-03-16 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-16 09:00:00 UTC to 2025-03-16 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-16 12:00:00 UTC to 2025-03-16 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-16 15:00:00 UTC to 2025-03-16 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 16, 15:00

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
Mar 13, 21:002025-03-13 21:00:00 UTC2025-03-14 00:00:00 UTC101
Mar 14, 00:002025-03-14 00:00:00 UTC2025-03-14 03:00:00 UTC000
Mar 14, 03:002025-03-14 03:00:00 UTC2025-03-14 06:00:00 UTC000
Mar 14, 06:002025-03-14 06:00:00 UTC2025-03-14 09:00:00 UTC000
Mar 14, 09:002025-03-14 09:00:00 UTC2025-03-14 12:00:00 UTC000
Mar 14, 12:002025-03-14 12:00:00 UTC2025-03-14 15:00:00 UTC000
Mar 14, 15:002025-03-14 15:00:00 UTC2025-03-14 18:00:00 UTC000
Mar 14, 18:002025-03-14 18:00:00 UTC2025-03-14 21:00:00 UTC211
Mar 14, 21:002025-03-14 21:00:00 UTC2025-03-15 00:00:00 UTC000
Mar 15, 00:002025-03-15 00:00:00 UTC2025-03-15 03:00:00 UTC000
Mar 15, 03:002025-03-15 03:00:00 UTC2025-03-15 06:00:00 UTC000
Mar 15, 06:002025-03-15 06:00:00 UTC2025-03-15 09:00:00 UTC000
Mar 15, 09:002025-03-15 09:00:00 UTC2025-03-15 12:00:00 UTC000
Mar 15, 12:002025-03-15 12:00:00 UTC2025-03-15 15:00:00 UTC000
Mar 15, 15:002025-03-15 15:00:00 UTC2025-03-15 18:00:00 UTC000
Mar 15, 18:002025-03-15 18:00:00 UTC2025-03-15 21:00:00 UTC000
Mar 15, 21:002025-03-15 21:00:00 UTC2025-03-16 00:00:00 UTC000
Mar 16, 00:002025-03-16 00:00:00 UTC2025-03-16 03:00:00 UTC000
Mar 16, 03:002025-03-16 03:00:00 UTC2025-03-16 06:00:00 UTC101
Mar 16, 06:002025-03-16 06:00:00 UTC2025-03-16 09:00:00 UTC000
Mar 16, 09:002025-03-16 09:00:00 UTC2025-03-16 12:00:00 UTC000
Mar 16, 12:002025-03-16 12:00:00 UTC2025-03-16 15:00:00 UTC000
Mar 16, 15:002025-03-16 15:00:00 UTC2025-03-16 18:00:00 UTC101

What Hacker News says

5 sources
You can quite often write C code that compilers will autovectorize into what you want.. if the thing in question is a simple case, or you put in effort into doing the non-trivial aspects yourself. e.g. for the loop reordering example [1] in C you could just, well, manually reorder the loops; and the simple loop would autovectorize to AVX2 just fine. The things that are messy-to-impossible to achieve in current traditional compilers are things where the compiler thinks it does a smart transformation, but it ends up making things worse. [1]: https://github.com/exo-lang/exo/tree/main/examples/avx2_matm...
In High-performance computing, with much less code
If you read the actual github, linked from the article, you will realize that it is a manual static scheduler. Example here: https://github.com/exo-lang/exo/blob/main/examples/avx2_matm... The hardware still does what it does, but this is a tool for manually ordering operations. I did, in fact, read the materials before dismissing them as useless, since this is very relevant to what I do professionally.
In Exo: Exocompilation for productive programming of hardware accelerators
> The researchers implemented a scheduling library with roughly 2,000 lines of code in Exo 2, encapsulating reusable optimizations that are linear-algebra specific and target-specific (AVX512, AVX2, Neon, and Gemmini hardware accelerators). This library consolidates scheduling efforts across more than 80 high-performance kernels with up to a dozen lines of code each, delivering performance comparable to, or better than, MKL, OpenBLAS, BLIS, and Halide. exo-lang/exo: https://github.com/exo-lang/exo
In High-performance computing, with much less code

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.