durin
Cwerg
durin | Cwerg | |
---|---|---|
3 | 59 | |
13 | 402 | |
- | - | |
0.0 | 9.6 | |
about 2 years ago | 6 days ago | |
Rust | Python | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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.
durin
-
Are there any low level, cross platform assembly languages that allow jumping to non labels?
So I think I may be one of the few people in the world who has actually implemented a GC using LLVM's statepoint infrastructure. It's poorly documented and there are some gotchas, but I'd say it's definitely usable, and it works with basically any collector design, including moving collectors (I'm using Immix) and has no runtime bookkeeping overhead and allows LLVM to optimize the code without worrying about GC, which is nice. It's actually gotten a bit better with LLVM 13, too. If you're curious what a LLVM-based GC looks like, mine is in this folder. Of course, if you just want some sort of GC, you can also just link it with Boehm which is quite easy and has pretty good performance - this is what e.g. Crystal does, although they're talking about switching.
-
September 2021 monthly "What are you working on?" thread
I also fixed lots of bugs in the GC and backend, so it should be a lot more stable now.
-
May 2021 monthly "What are you working on?" thread
Recently, I've been working on adding garbage collection to Pika. I've successfully written an Immix-based garbage collector that works with the LLVM GC support infrastructure, and I'm currently working on integrating the GC with Pika, or really Durin, the dependently-typed intermediate representation that Pika compiles to. Because types are passed around at runtime, objects of unknown type and size can be stored unboxed in polymorphic data structures; but that makes keeping track of type information for heap allocations somewhat harder, because type information needs to be allocated and constructed at runtime in some cases. It's an interesting design problem, because you want constructing type information to be fast; but the GC will run much more often, so maximizing tracing speed by avoiding e.g. indirection in type information is important; and you also want to construct as much type information as possible at compile time and embed it as constants.
Cwerg
-
Cwerg: C-like language that can be implemented in 10kLOC
Perhaps these have already been dealt with and I'm missing critical information. If so, my apologies. Great work, in any case.
[1] https://github.com/robertmuth/Cwerg/tree/master/FrontEnd#dis...
-
Where can I find resources and guides on how to build compiler backends?
Cwerg has backend that can be used as JIT and is written with readability in mind. Additional documentation can be found here: https://github.com/robertmuth/Cwerg/tree/master/Docs
- Most important language features not touched in the book "Crafting Interpreters"?
- Lack of resources in creating Assemblers from scratch.
-
Minimum ISA Capabilities to Support Most (Non-Interactive) Programs?
I defined a basic ISA-like IR for Cwerg. It has unlimited registers and no constraints on immediates.
-
How do you design a compiler and a language?
entire compiler front end ast nodes
-
Syntax Design
I was also going down the path of bike shedding concrete syntax for my language Cwerg before pulling the plug on that effort and just using s-exprs. I managed to make the s-expr quite succinct by carefully choosing the order of arguments so I can omit optional ones. Also very helpful was to use square brackets for list, e.g. (call fun-name [arg1 arg2]). This simplifies parsing a little bit and is easier on the eye. Here are some Code Examples
-
November 2022 monthly "What are you working on?" thread
I am iterating over the languages features for Cwerg's Frontend which aims to be a low level language with about the complexity of C but with some of the comforts of modern languages. I am especially happy with the choice of adding sum types. Relative to C the current feature set looks like this: Removed: * arrays decay to pointers * bitfields * separate compilation (more of a backend issue) * pre-processor * varargs * implcit type conversions * (untagged) unions * ++/-- * comma operator * implicitly nullable pointers * goto
- typed asts and codegen
- Features Compendium
What are some alternatives?
c3c - Compiler for the C3 language
mir - A lightweight JIT compiler based on MIR (Medium Internal Representation) and C11 JIT compiler and interpreter based on MIR
bluebird - A work-in-progess programming language modeled after Ada and C++
tinycc - Unofficial mirror of mob development branch
never - Never: statically typed, embeddable functional programming language.
asmjit - Low-latency machine code generation
konna - A fast functional language based on two level type theory
pika - A WIP little dependently-typed systems language
asmdb - Instructions database and utilities for X86/X64 and ARM (THUMB/A32/A64) architectures.
imp - Imp is a statically typed and compiled scripting language with the goal of increasing programmer confidence.
boring-lang - A very boring programming language