Our great sponsors
oasis | chibicc | |
---|---|---|
26 | 21 | |
2,701 | 8,504 | |
1.9% | - | |
8.8 | 0.0 | |
8 days ago | 6 months ago | |
Roff | 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.
oasis
- Oasis – a small, statically-linked Linux system
-
After tens of hours and a numerous amount of coffee, I proudly did it
You reminded me for trying Oasis: https://github.com/oasislinux/oasis
-
Idea: Steam should delete all native Linux ports from its library to prevent ABI breakage issues and SteamOS should be made into a statically linked OS
IMO, would eliminate issues with glibc and other libraries breaking ABI compatibility. Statically-linked distros like oasis could be used as inspiration.
-
An estimation of what distros and desktops have the largest userbase?
Oasis and its native desktop Velox.
-
Compile webkit2gtk to be as minimal as possable.
I wonder why suckless team chose to build its browser on webkit2gtk instead of NetSurf, things like these and others like their adherence to Xorg makes me think seriously to move to Framebuffer (fbpad, fbpdf, fbff ..) or Oasis (Wayland + SWC + Velox).
- In theory, could you compile all of the libraries required to run a Linux environment into a single, massive .so file?
-
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).
- Oasis。小型静态链接的Linux系统 (Oasis: Small statically-linked Linux system)
- Oasis: Small statically-linked Linux system
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?
iglunix - Linux (and other kernels) distro with no GNU components
8cc - A Small C Compiler
glaucus - A simple and lightweight Linux® distribution based on musl libc and toybox
mold - Mold: A Modern Linker 🦠
Ceedling - Ruby-based unit testing and build system for C projects
build-your-own-x - Master programming by recreating your favorite technologies from scratch.
muslrust - Docker environment for building musl based static linux rust binaries
SmallerC - Simple C compiler
kiss - KISS Linux - Package Manager
Co-dfns - High-performance, Reliable, and Parallel APL
Sourcetrail - Sourcetrail - free and open-source interactive source explorer
quickjs - Public repository of the QuickJS Javascript Engine.