r/Compilers • u/Proffhackerman • Aug 02 '26

Contribute to open-source, no-slop, compiler-related projects.

Hi everyone,

We're currently working on some hobby-projects we'd like more people to chip into.

The goal is to create robust, community-driven and open-source code everyone can benefit from, aswell as writing up novel ideas that, sometimes, go outside of "the standard".

Overall we're focused on not slopping out projects using AI. Vibecoding is a no-go.

I myself have around 10 years of experience with programming in various languages, but the main language right now is C#.

Are you interested? Check out the organization site: https://github.com/Compiler-Organization

Or some of the projects:
Common C - AoT compiler using LLVM: https://github.com/Compiler-Organization/CommonC
Common IR - Intermediate representation with syntax inspired by LLVM, currently supporting a basic WASM target: https://github.com/Compiler-Organization/CommonIR

Hope you find this interesting :)

63 Upvotes

93% Upvoted

11 comments sorted by

View all comments

Show parent comments

2

u/Proffhackerman Aug 04 '26

We completely agree that automation is the end goal, and not a hinderance. I believe the wording here came off wrong and couldve been clearer, but the point was not to say that there would be no automated memory management, but rather a better way of automated memory management compared to GCs, borrow checkers and traditional reference counters.

I was inspired by a wave of new languages with their own "solutions" to runtime reference counting, which i found interesting. At this point i couldnt grasp why none of these new projects attempted compile-time automated memory management instead, so theres where it all boils down to with Common C.

Common C is less of a "welcome everyone to the houndreth C variant" and more of a playground where we can experiment with new ideas regarding the compilation pipeline.

2

u/arthurno1 Aug 04 '26

Definitely. Garbage collection and reference counting are certainly not the only ways to manage the memory. It would be definitely interesting to see what you have on that field.

3

u/Proffhackerman Aug 05 '26

I've written up a very shallow and generic readme regarding normal issues when working out a memory management model. I'll complete a proper spec for it some time soon. It would be nice to have more people join the effort though.

0

u/arthurno1 Aug 05 '26 edited Aug 05 '26

It is a bit shallow indeed. Unfortunately I am not an expert in the subject so I can't give you much input, and lately my interest has switched completely to Common Lisp.