pycopy-lib
chibicc
Our great sponsors
pycopy-lib | chibicc | |
---|---|---|
7 | 21 | |
241 | 8,504 | |
- | - | |
6.2 | 0.0 | |
7 months ago | 6 months ago | |
Python | C | |
GNU General Public License v3.0 or later | 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.
pycopy-lib
-
Pycopy 3.5.4 - a minimalist and memory-efficient Python dialect
So, unlike MicroPython itself, which was started by another guy, micropython-lib was started and largely done by me (but initially contributed it to the micropython project, yeah). I continue that work in https://github.com/pfalcon/pycopy-lib
In this version, improvements in native types subclassing support. Pycopy standard library, https://github.com/pfalcon/pycopy-lib, also sees further development and improvements.
-
Pycopy 350 A Minimalist And Memoryefficient
Plug pure-Python bytecode (or JIT) compiler: https://github.com/pfalcon/pycopy-lib/tree/master/ucompiler (prototype/WIP)
-
Pycopy 3.5.0 - a minimalist and memory-efficient Python dialect
Plug pure-Python bytecode (or JIT) compiler: https://github.com/pfalcon/pycopy-lib/tree/master/ucompiler (prototype/WIP)
-
Bootstrapping Case Studies
Thanks. Except it's not mine, but CPython2's stdlib module (written by many people) ported to Python3.5. What's mine is Pycopy stdlib ucompiler module: https://github.com/pfalcon/pycopy-lib/tree/master/ucompiler, written by me from scratch based on the experience with CPython2's module (I figured I'd have better time writing one from scratch than cleaning up CPython2's module).
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?
micropython-lib - Core Python libraries ported to MicroPython
8cc - A Small C Compiler
picoweb - Really minimal web application framework for the Pycopy project (minimalist Python dialect) and its "uasyncio" async framework
mold - Mold: A Modern Linker 🦠
pycopy - Pycopy - a minimalist and memory-efficient Python dialect. Good for desktop, cloud, constrained systems, microcontrollers, and just everything.
build-your-own-x - Master programming by recreating your favorite technologies from scratch.
IntercalScript - The IntercalScript programming language
SmallerC - Simple C compiler
python-imphook - Simple and clear import hooks for Python - import anything as if it were a Python module
Co-dfns - High-performance, Reliable, and Parallel APL
python-compiler - A Python bytecode compiler written in Python. This repository is now a fork of https://github.com/facebookincubator/python-compiler, upstream is there.
quickjs - Public repository of the QuickJS Javascript Engine.