llvm-project
Graal
Our great sponsors
llvm-project | Graal | |
---|---|---|
346 | 155 | |
24,910 | 19,678 | |
3.9% | 1.2% | |
10.0 | 10.0 | |
6 days ago | 6 days ago | |
C++ | Java | |
GNU General Public License v3.0 or later | 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.
llvm-project
-
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.
-
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?
> Take for example CVE-2022-21658 (https://blog.rust-lang.org/2022/01/20/cve-2022-21658.html) in Rust, related to a filesystem API. 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.
That just plain wrong. Just simply wrong. And I hope it is not a lie done on purpose.
The C++ community acknowledge the issue as soon as the Rust one posted the problem and issued a fix which is already deployed with major compilers [^1] [^2]
It does not have a CVE associated since the issue was spotted within Rust stdlib first.
This is this exact kind of FUD and zealotism that makes people hate the Rust community. I wish the community mature a bit on this aspect.
[^1]: https://github.com/gcc-mirror/gcc/commit/ebf6175464768983a2d...
[^2]: https://github.com/llvm/llvm-project/commit/4f67a909902d8ab9...
-
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...
-
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-...
-
MRISC32 – An Open 32-Bit RISC/Vector ISA (Suitable for FPGA CPU)
Looks like llvm recently got some fusion support via -mtune now: https://github.com/llvm/llvm-project/commits/main/llvm/lib/T...
-
Std: Clamp generates less efficient assembly than std:min(max,std:max(min,v))
https://github.com/llvm/llvm-project/issues/57589
Turn on fast-math, it flips the FTZ/DAZ bit for the entire application. Even if you turned it on for just a shared library!
Graal
- FLaNK Stack 05 Feb 2024
-
Apple releases Pkl – onfiguration as code language
Pkl was built using the GraalVM Truffle framework. So it supports runtime compilation using Futurama Projections. We have been working with Apple on this for a while, and I am quite happy that we can finally read the sources!
https://github.com/oracle/graal/tree/master/truffle
Disclaimer: graalvm dev here.
-
Quarkus 3.4 - Container-first Java Stack: Install with OpenJDK 21 and Create REST API
Quarkus is one of Java frameworks for microservices development and cloud-native deployment. It is developed as container-first stack and working with GraalVM and HotSpot virtual machines (VM).
-
Level-up your Java Debugging Skills with on-demand Debugging
Apologies, I didn't mean to imply DCEVM went poof, just that I was sad it didn't make it into OpenJDK so one need not do JDK silliness between the production one and the "debugging one" since my experience is that's an absolutely stellar way to produce Heisenbugs
And I'll be straight: Graal scares me 'cause Oracle but I just checked and it looks to the casual observer that it's straight-up GPLv2 now so maybe my fears need revisiting: https://github.com/oracle/graal/blob/vm-23.1.0/LICENSE
-
Rust vs Go: A Hands-On Comparison
> to be compiled to a single executable is a strength that Java does not have
I think this is very outdated claim: https://www.graalvm.org/
- Leveraging Rust in our high-performance Java database
- Java 21 makes me like Java again
-
A JVM in Rust part 5 – Executing instructions
Why would they? The direction for safer JVM research is to implement JVMs in Java, which has the advantage of being both memory safe outside a few tiny core areas (same as rust) whilst having cleaner code than the Rust impl (none of these problems with lifetimes).
See here: https://github.com/oracle/graal/tree/master/substratevm/src
-
A History of Clojure (2020) [pdf]
Ah, yeah, that's probably a bit far off in the future. Probably would be possible via GraalVM once GC is available, https://github.com/oracle/graal/issues/3391
-
How can I integrate a Svelte(Kit?) frontend on a Spring Boot application?
In short, you need to use graalvm and install the nodejs plugin for it (guide here).
What are some alternatives?
Liberica JDK - Free and 100% open source Progressive Java Runtime for modern Javaâ„¢ deployments supported by a leading OpenJDK contributor
Adopt Open JDK - Eclipse Temurinâ„¢ build scripts - common across all releases/versions
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
awesome-wasm-runtimes - A list of webassemby runtimes
maven-jpackage-template - Sample project illustrating building nice, small cross-platform JavaFX or Swing desktop apps with native installers while still using the standard Maven dependency system.
SAP Machine - An OpenJDK release maintained and supported by SAP
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
teavm - Compiles Java bytecode to JavaScript, WebAssembly and C
Quarkus - Quarkus: Supersonic Subatomic Java.
Lark - Lark is a parsing toolkit for Python, built with a focus on ergonomics, performance and modularity.
JDK - JDK main-line development https://openjdk.org/projects/jdk
gcc