Rust-Written Linux Scheduler Showing Promising Results For Gaming PerformanceChewy@discuss.tchncs.de to Linux@lemmy.ml – 178 points – 9 months agonitter.netPhoronix18Post a CommentPreviewYou are viewing a single commentView all commentsNow if only gccrs would mature soon! LLVM-based is fine for most case, but I bet a lot of people would want to stick with gcc for compiling the kernel.For that usecase rustc_codegen_gcc works too and is much more likely to be mature soon.It seems to still require LLVM, thoWhat makes you think that? The whole point of it is to create a rustc backend that uses libgccjit instead of LLVM.
Now if only gccrs would mature soon! LLVM-based is fine for most case, but I bet a lot of people would want to stick with gcc for compiling the kernel.For that usecase rustc_codegen_gcc works too and is much more likely to be mature soon.It seems to still require LLVM, thoWhat makes you think that? The whole point of it is to create a rustc backend that uses libgccjit instead of LLVM.
For that usecase rustc_codegen_gcc works too and is much more likely to be mature soon.It seems to still require LLVM, thoWhat makes you think that? The whole point of it is to create a rustc backend that uses libgccjit instead of LLVM.
It seems to still require LLVM, thoWhat makes you think that? The whole point of it is to create a rustc backend that uses libgccjit instead of LLVM.
What makes you think that? The whole point of it is to create a rustc backend that uses libgccjit instead of LLVM.
Now if only gccrs would mature soon!
LLVM-based is fine for most case, but I bet a lot of people would want to stick with gcc for compiling the kernel.
For that usecase
rustc_codegen_gccworks too and is much more likely to be mature soon.It seems to still require LLVM, tho
What makes you think that? The whole point of it is to create a
rustcbackend that useslibgccjitinstead of LLVM.