Our great sponsors
acwj | chibicc | |
---|---|---|
25 | 21 | |
9,852 | 8,514 | |
- | - | |
2.8 | 0.0 | |
3 months ago | 6 months ago | |
C | C | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
acwj
-
Toy C compiler, worth having an IR stage?
I wrote https://github.com/DoctorWkt/acwj. I'm working on a version with an IR so I can add some optimisations to it. I'd say, yes, have an IR :-)
-
Resources for beginners
Here's another resource: https://github.com/DoctorWkt/acwj
-
Why Take a Compiler Course?
I currently study https://github.com/DoctorWkt/acwj which is quite interesting I have to admit.
I'm interested in this topic, because I want to participate in TinyC compiler's development; I use it quite often to run C demos of mine and its execution is instant.
The least I can do is to either fix bugs or extend it to support more C99, C11, C17 features, and why not even C23 as soon as it gets approved?
All I need is to gain the necessary knowledge and experience to jump right in and start fixing things.
- Any good references/tutorials/text’s for building a compiler?
- A Compiler Writing Journey
- Why does Rust have parameters on impl?
-
Toy languages for implementing a compiler.
I took a journey writing my first compiler, and started with just evaluating integer expressions. From there, I moved to adding language features and ended up with a compiler that could compile itself: https://github.com/DoctorWkt/acwj
- Acwj - A Compiler Writing Journey
chibicc
- Cwerg: C-like language that can be implemented in 10kLOC
- Apple hiring compiler developers for improving Swift / C++ interoperability
-
GCC always assumes aligned pointer accesses
If a --k&r mode was to be reliable, wouldn't it need to get specified first? Otherwise people would start relying on some edge case.
If speed is not a requirement for the --k&r mode, you could just take the tis-interpreter and note that if it runs without UB, it is still much faster than an actual computer was when k&r were active.
Would it even be possible to specify a variant of C that contains no UB (e.g. would define exactly what happens on unaligned access), but can compile practical existing C89 programs? I wonder if it could be written such that it could actually specify the behaviour consistently across the language intersection supported by both of e.g. GCC 2.95 and Chibicc[0].
Or maybe there are so many bugs in GCC 2.95 that it would simply be infeasible? How much time would it take to specify?
[0]: https://github.com/rui314/chibicc
-
EU to vote regulation that has a considerable potential to hurt OSS
I was on the Eclipse Foundation call a few days ago regarding this topic and they said there was a well-established 3-part test for this in the EU courts. But I don't think I managed to take a screenshot, sorry.
Here is a snippet from the EU Blue Guide linked the from the Eclipse blog post:
"Commercial activity is understood as providing goods in a business related context. Non-profit organisations may be considered as carrying out commercial activities if they operate in such a context. This can only be appreciated on a case by case basis taking into account the regularity of the supplies, the characteristics of the product, the intentions of the supplier, etc. In principle, occasional supplies by charities or hobbyists should not be considered as taking place in a business related context."
I would consider GCC or React to fit this definition, while a hobby project like https://github.com/rui314/chibicc not to fit it.
-
Best practice to store context for a C compiler
chibicc
-
SectorC: A C Compiler in 512 bytes
chibicc: https://github.com/rui314/chibicc (A reasonably digestible C implementation)
- List of (open source) C compilers
- Chibicc – A Small C Compiler
-
Are Hoistings Possible for C++?
When you say a fork of LLVM, am I correct in assuming that you specifically mean a fork of Clang? I don't see how the compiler backend would affect support for language extensions, regardless of whether it's an exception to that such as Tcc, Cproc, the MIR C jitter, lacc, 8cc, 9cc, and chibicc. Most of those are not for production, excluding Cproc and Tcc (at least according to Suckless or Oasis).
What are some alternatives?
nelua-lang - Minimal, efficient, statically-typed and meta-programmable systems programming language heavily inspired by Lua, which compiles to C and native code.
8cc - A Small C Compiler
os-tutorial - How to create an OS from scratch
mold - Mold: A Modern Linker 🦠
dnsguide - A guide to writing a DNS Server from scratch in Rust
build-your-own-x - Master programming by recreating your favorite technologies from scratch.
write-a-C-interpreter - Write a simple interpreter of C. Inspired by c4 and largely based on it.
SmallerC - Simple C compiler
jonesforth - Mirror of JONESFORTH
Co-dfns - High-performance, Reliable, and Parallel APL
the-super-tiny-compiler - :snowman: Possibly the smallest compiler ever
quickjs - Public repository of the QuickJS Javascript Engine.