coollang-2020-fs
llvm-project
Our great sponsors
coollang-2020-fs | llvm-project | |
---|---|---|
5 | 348 | |
37 | 25,314 | |
- | 3.1% | |
9.2 | 10.0 | |
3 months ago | 7 days ago | |
F# | C++ | |
MIT License | GNU General Public License v3.0 or later |
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.
coollang-2020-fs
-
Course using F#: Write your own tiny programming system(s)
Looks interesting.
Once I saw it's a Czech university course using F#, I knew Tomáš Petříček would be the lecturer :)
A couple years back, I wrote a compiler of tiny-ish scala subset in F# (the code is imperative, though)[1]
-
Compiler of a small Scala subset into x86-64 assembly, in F#
The repo is on github: https://github.com/mykolav/coollang-2020-fs
-
Compiling a small Scala subset into x86-64 assembly
Go to the project's repository to explore the source code.
- Compiling a small Scala subset into x86-64 asm
-
Compiler Class
You might find [CS 6120: Advanced Compilers: The Self-Guided Online Course][1] interesting. I'm slowly working through it, but basically its focus is intermediate representations, optimizations, etc. A link to the course was on the first page of HN some time ago.
Also -- and you knew it was coming -- I've written a [toy-compiler of a Scala subset][2] myself :)
I'm new to F# and writing compilers, so I'm sure the code is full of rookie mistakes. Still, it works and does generate assembly and executables for Linux and Windows.
[1]: https://www.cs.cornell.edu/courses/cs6120/2020fa/self-guided...
llvm-project
- Flang-new: How to force arrays to be allocated on the heap?
- The LLVM Compiler Infrastructure
-
Programming from Top to Bottom - Parsing
You can never mistake type_declaration with an identifier, otherwise the program will not work. Aside from that constraint, you are free to name them whatever you like, there is no one standard, and each parser has it own naming conventions, unless you are planning to use something like LLVM. If you are interested, you can see examples of naming in different language parsers in the AST Explorer.
-
Look ma, I wrote a new JIT compiler for PostgreSQL
> There is one way to make the LLVM JIT compiler more usable, but I fear it’s going to take years to be implemented: being able to cache and reuse compiled queries.
Actually, it's implemented in LLVM for years :) https://github.com/llvm/llvm-project/commit/a98546ebcd2a692e...
-
C++ Safety, in Context
> It's true, this was a CVE in Rust and not a CVE in C++, but only because C++ doesn't regard the issue as a problem at all. The problem definitely exists in C++, but it's not acknowledged as a problem, let alone fixed.
Can you find a link that substantiates your claim? You're throwing out some heavy accusations here that don't seem to match reality at all.
Case in point, this was fixed in both major C++ libraries:
https://github.com/gcc-mirror/gcc/commit/ebf6175464768983a2d...
https://github.com/llvm/llvm-project/commit/4f67a909902d8ab9...
So what C++ community refused to regard this as an issue and refused to fix it? Where is your supporting evidence for your claims?
-
Clang accepts MSVC arguments and targets Windows if its binary is named clang-cl
For everyone else looking for the magic in this almost 7k lines monster, look at line 6610 [1].
[1] https://github.com/llvm/llvm-project/blob/8ec28af8eaff5acd0d...
-
Rewrite the VP9 codec library in Rust
Through value tracking. It's actually LLVM that does this, GCC probably does it as well, so in theory explicit bounds checks in regular C code would also be removed by the compiler.
How it works exactly I don't know, and apparently it's so complex that it requires over 9000 lines of C++ to express:
https://github.com/llvm/llvm-project/blob/main/llvm/lib/Anal...
- Fortran 2023
-
MiniScript Ports
• Go • Rust • Lua • pure C (sans C++) • 6502 assembly • WebAssembly • compiler backends, like LLVM or Cranelift
-
On Avoiding Register Spills in Vectorized Code with Many Constants
Compilers also may even spill data to stack from memory, even when the original location is still available, as can be seen in this issue: https://github.com/llvm/llvm-project/issues/53348
I vaguely remember that spilling like this could allow high-end CPUs to use something similar to register renaming, i.e. stack locations like [rsp + 96] could be stay in a physical registers during function execution (high-end CPUs often have more physical registers, than logical ones), but could find good references whether such optimization exists in practice or not.
Unfortunately, I think more often than note it causes performance regressions and in some cases it may even cause unnecessary stack spilling of sensitive data: https://github.com/rust-lang/rust/issues/88930#issuecomment-...
What are some alternatives?
selfie - An educational software system of a tiny self-compiling C compiler, a tiny self-executing RISC-V emulator, and a tiny self-hosting RISC-V hypervisor.
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
shecc - A self-hosting and educational C optimizing compiler
Lark - Lark is a parsing toolkit for Python, built with a focus on ergonomics, performance and modularity.
proc - Procedural Intel x86_64 compiler from scratch, inspired by Fortran, Pascal and Assembly.
gcc
scamp-cpu - A homebrew 16-bit CPU with a homebrew Unix-like-ish operating system.
SDL - Simple Directmedia Layer
jet - A Fast C and Python like Programming Language that puts the Developer first. WIP
cosmopolitan - build-once run-anywhere c library
Fable: F# |> BABEL - F# to JavaScript, TypeScript, Python, Rust and Dart Compiler
STL - MSVC's implementation of the C++ Standard Library.