Committing to Rust for Kernel Code

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

CodeRabbit: AI Code Reviews for Developers
Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
coderabbit.ai
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
  1. linux

    Linux kernel source tree (by ClangBuiltLinux)

    > Torvalds answered that, while he used to find problems in the LLVM Clang compiler, now he's more likely to find problems with GCC instead; he now builds with Clang.

    https://github.com/ClangBuiltLinux/linux/issues is our bug tracker for known issues (a few are tracked in llvm's issue tracker). Bug reporters and future kernel hackers wanted!

    As I mentioned on mastodon, there's lots of bugs still to be fixed everywhere, but even if we don't fix them, providing competition in the toolchain space has been worth it to users.

  2. CodeRabbit

    CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

    CodeRabbit logo
  3. linux

    Linux kernel source tree (by AsahiLinux)

    > Is this mostly just a thing to get more young people interested in kernel development...allowing them to start out in less important areas and in a language they are passionate about?

    Not likely. At the moment you need to do extra work to get Rust working well. It's not exactly beginner friendly and doing work in the kernel, you'll need to dig into C anyway.

    > Or is this a serious proposal about the future of operating systems and other low level infrastructure code?

    Serious code already exists, so... Yes?

    > Do you just program everything in unsafe mode? What about runtimes?

    Why would you? You need that only when interfacing with something that can't hold the Rust compiler assumptions. See for example https://github.com/AsahiLinux/linux/blob/gpu/rebase-6.4/driv...

    The few places that need direct access / unsafe are almost all single-line areas with an explanation.

  4. serde

    Serialization framework for Rust

  5. static-clang

    Statically-linked clang distribution. Uses musl libc on Linux and only depends on libSystem on OSX

    https://github.com/dzbarsky/static-clang should let you build it in a reproducible way with a single command.

  6. gcc

    GCC is also written in C++, and has had C++ deps since 2013:

    https://github.com/gcc-mirror/gcc/blob/master/gcc/c/c-parser...

  7. SaaSHub

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    SaaSHub logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • ISO C became unusable for operating systems development

    8 projects | news.ycombinator.com | 21 Jan 2022
  • What (not how) to contribute to the kernel

    2 projects | /r/kernel | 8 Dec 2021
  • Here are LLVM 13 and Clang 13 compiled release binaries for Ubuntu 16.04, if anyone needs them!

    1 project | /r/LLVM | 6 Oct 2021
  • Show HN: LLVM 13 and Clang 13 compiled release binaries for Ubuntu 16.04

    1 project | news.ycombinator.com | 6 Oct 2021
  • Intel C/C++ compilers complete adoption of LLVM

    2 projects | news.ycombinator.com | 12 Aug 2021

Did you know that C is
the 6th most popular programming language
based on number of references?