wincs
A Rust wrapper for the Windows Cloud Filter API (by ok-nick)
inkwell
It's a New Kind of Wrapper for Exposing LLVM (Safely) (by TheDan64)
wincs | inkwell | |
---|---|---|
1 | 16 | |
11 | 2,154 | |
- | - | |
0.6 | 8.2 | |
6 days ago | 4 days ago | |
Rust | Rust | |
MIT License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
wincs
Posts with mentions or reviews of wincs.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-03.
-
Rust for Windows.
I’ve been working on a safe wrapper around the Cloud Filter API using the windows crate. I’m definitely planning on moving to windows-sys to cut down on compile times (I’ve seen a significant difference), but check it out if you’re interested, https://github.com/ok-nick/wincs
inkwell
Posts with mentions or reviews of inkwell.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-08-04.
-
Compiler Optimization Learning Suggestions
Secondly, I have learned about LLVM, and I have learned about the Inkwell library on Rust (It's a New Kind of Wrapper for Exposing LLVM (Safely)). Has anyone used this library before? Is this a good practice? Is it suitable for my compiler? Can I write some optimization passes of my own using this library?
-
Finding LLVM location for use with the inkwell Rust crate
I am trying to use the inkwell Rust crate for working with LLVM. In Cargo.toml, I have specified the LLVM version using features = ["llvm15-0"]
-
How Rust transforms into Machine Code.
inkwell is a great llvm binding for rust and it has an implementation of kaleidoscope
- Inkwell – New Kind of Wrapper for Exposing LLVM in Rust
-
Need help improving API for crate relying on Inkwell (Self-referential struct alternative)
I'm working on a compiler that uses the LLVM wrapper Inkwell for compilation. In order to compile something in inkwell, unless I'm missing something (which I very well might be), you need two structs:
-
Tools for creating a programming language in rust
Compiler backends (If building JIT/machine compiled langauges) 1. cranelift 2. inkwell - safe rust wrapper around llvm
-
How do I instrument LLVM IR for a Rust program?
Haha small world. I think we go to the same university and I took the same or similar course a few years ago. If somebody hasn't done the work for you, you may have to do some instrumentation yourself depending on what you want to track IMO https://github.com/TheDan64/inkwell is the best LLVM wrapper for Rustland (Python's llvmlite is a bit easier to use though)
-
How good is LLVM in other languages other than C++? (In my case I'm interested in using Rust)
I'm currently using the Inkwell bindings for Rust, which I've found actually pretty nice. In terms of generating LLVM IR, the C bindings (which is what Inkwell uses internally) can do anything you want them to (definitely not limited to trivial languages as someone else here said.) I'm even using the LLVM garbage collection infrastructure, with no problems (well, no problems in generating it; the LLVM GC infrastructure works pretty well but is sparsely documented, so actually writing a GC is fairly difficult, but it's doable). The C bindings are actually more stable than the C++ bindings (!), although not quite as stable as the textual IR format; but without the bindings you would have to write code to generate the IR yourself, the compiler would be slower as it must be emitted as text and then reparsed in a different process, and you would have less control over optimization.
-
Are there any repos of tutorials on writing a compiler in Rust?
safe llvm bindings https://github.com/TheDan64/inkwell
-
LLVM Infrastructure and Rust
As we reviewed in this article LLVM IR has many use-cases and allows us to analyze and optimize source code through its passes. Knowing IR language itself will help us to write our passes and build projects around it for debugging, testing, optimizing. Currently, LLVM IR doesn't have Rust API. It's mainly used through the C++ library. However, some user-created repos are available on crates.io. There is a Rust binding to LLVM's C API - llvm-sys and two other, more Rusty APIs that are using LLVM: inkwell and llvm-ir. And finally, if you want to learn how to write a LLVM pass you should start here.