4 ms·
The Rust portability issue is the reason I have been pushing forward with the new M68k backend for LLVM which is due to be merged shortly: > https://github.com
by cbmuser 6y ago
The Rust portability issue is the reason I have been pushing forward with the new M68k backend for LLVM which is due to be merged shortly:
> https://github.com/M680x0/M680x0-mono-repo https://github.com/M680x0/M680x0-mono-repo
Patches for the M68k backend are discussed on reviews.llvm.org.
I have also started a Rust port for m68k already that depends on the LLVM backend work above:
> https://github.com/glaubitz/rust/tree/m68k-linux https://github.com/glaubitz/rust/tree/m68k-linux
For other architectures, the goal is to get gccrs moving forward and merged upstream:
> https://github.com/philberty/gccrs/ https://github.com/philberty/gccrs/
For anyone interested in helping, there are Bountysource campaigns I started to support both efforts:
> https://www.bountysource.com/issues/90829856-llvm-complete-the-m68000-backend-so-it-can-be-merged-upstream https://www.bountysource.com/issues/90829856-llvm-complete-t...
> https://www.bountysource.com/issues/86138921-rfe-add-a-frontend-for-the-rust-programming-language https://www.bountysource.com/issues/86138921-rfe-add-a-front...
- JoshTriplett 6y ago> For other architectures, the goal is to get gccrs moving forward and merged upstream: I would much rather see rustc_codegen_gcc upstreamed: https://github.com/antoyo/rustc_codegen_gcc https://github.com/antoyo/rustc_codegen_gcc A GCC backend for rustc would provide all the code generation of GCC without duplicating the Rust frontend.
- cbmuser 6y agoI have no particular preference for either solution on the GCC side and this particular project is new to me. Will add it to my list of projects I keep an eye on. FWIW, I think gccrs also tries to use the Rust frontend if I remember correctly.