corrode
C to Rust translator (by jameysharp)
llvm-cbe
resurrected LLVM "C Backend", with improvements (by JuliaHubOSS)
corrode | llvm-cbe | |
---|---|---|
3 | 14 | |
2,143 | 790 | |
- | 0.9% | |
0.0 | 6.5 | |
about 5 years ago | 6 days ago | |
Haskell | C++ | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
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.
corrode
Posts with mentions or reviews of corrode.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-02-01.
-
C2rust: Transpile C to Rust
Back in the day there was also Corrode: https://github.com/jameysharp/corrode
-
lipstick: a Rust-like syntax frontend for C
Some intersection with https://github.com/jameysharp/corrode in theory right? Maybe it's saner actually to start with corrode-to-lipstick (there has to be a good project name here) and then it's perhaps easier to turn lipstick into safe Rust?
- Modern C and What We Can Learn from It [video]
llvm-cbe
Posts with mentions or reviews of llvm-cbe.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-30.
-
Ask HN: LLVM vs. C
So how does the LLVM C backend work then?
https://github.com/JuliaHubOSS/llvm-cbe
-
rust to c complication?
One alternative worth mentioning, though, would be the LLVM C Backend maintained by the Julia community.
-
Programming language that compiles to clean C89 or C99?
If you drop "easily" and "human" (/s) from your requirements list, then the C backend for LLVM might work. Then you can choose any programming language you want that has LLVM 10-compatible frontend.
-
Easy way to convert a C++ library into straight C ?
If you really must have something that compiles in C (e.g. for a platform where you only have a C compiler) there's an LLVM backend that outputs C code: https://github.com/JuliaComputingOSS/llvm-cbe
- Snowman native code to C/C++ decompiler for x86/x86_64/ARM
-
Can Rust do every low level stuff C/C++ do?
You can convert llvm bitcode to C and then use C compiler, there is such project https://github.com/JuliaComputingOSS/llvm-cbe .
-
lipstick: a Rust-like syntax frontend for C
I'm really surprised that the LLVM C backends have continually been resurrected then abandoned over the years. It's a good solution to this sort of thing and would enable a lot of cool stuff like Rust to weird embedded platforms. The most recent one is the Julia backend: https://github.com/JuliaComputingOSS/llvm-cbe
-
C++ to C converter?
Check this project out: https://github.com/JuliaComputingOSS/llvm-cbe.
-
Show HN: prometeo – a Python-to-C transpiler for high-performance computing
Well IMO it can definitely be rewritten in Julia, and to an easier degree than python since Julia allows hooking into the compiler pipeline at many areas of the stack. It's lispy an built from the ground up for codegen, with libraries like (https://github.com/JuliaSymbolics/Metatheory.jl) that provide high level pattern matching with e-graphs. The question is whether it's worth your time to learn Julia to do so.
You could also do it at the LLVM level: https://github.com/JuliaComputingOSS/llvm-cbe
For interesting takes on that, you can see https://github.com/JuliaLinearAlgebra/Octavian.jl which relies on loopvectorization.jl to do transforms on Julia AST beyond what LLVM does. Because of that, Octavian.jl beats openblas on many linalg benchmarks
-
Writing a SQLite clone from scratch in C
You can try your luck with the "resurrected" C backend: https://github.com/JuliaComputingOSS/llvm-cbe
I don't understand why I see so many requests for LLVM-based languages to change around their backend or IR, that seems to be a huge amount of work for comparatively little benefit. The correct thing to do there is to just add support for those to LLVM.