GCC 13 and the State of Gccrs

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

InfluxDB high-performance time series database
Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.
influxdata.com
featured
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
  1. rustc_codegen_gcc

    libgccjit AOT codegen for rustc

    gcc-rs is one of two projects for bringing Rust to gcc. gcc-rs is the more ambitious of the two, with an entirely new frontend. There is also rustc_codegen_gcc (https://github.com/rust-lang/rustc_codegen_gcc) that keeps the rustc frontend, and only swaps out LLVM for GCC at the codegen stage.

  2. InfluxDB

    InfluxDB high-performance time series database. Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.

    InfluxDB logo
  3. rust

    Empowering everyone to build reliable and efficient software.

    > The underspecified part should not be a deal breaker, even though it's certainly a difficulty. But it will also be an opportunity to spot suboptimal implementation choices in rustc. Exposing these will improve the language as a whole.

    but... we don't want same sourcecode compile with a compiler implementation, but not another, right?

    When I say "under-specified", I meant something like this:

    https://github.com/rust-lang/rust/pull/105300/

    > I claim it's more correct as well because it fixes #104639.

    There is no spec. Just a bunch of implementation-defined behavior. Without a spec, this would be a forever catching up game. It is not easy to come up with a spec -- the implement is filled with heuristics because the intrinsic NP-completeness.

  4. gccrs

    GCC Front-End for Rust

    - But this misses so much extra context information

    3. Macro invocations there are really subtle rules on how you treat macro invocations such as this which is not documented at all https://github.com/Rust-GCC/gccrs/blob/master/gcc/rust/expan...

    Some day I personally want to write a blog post about how complicated and under spec'd Rust is, then write one about the stuff i do like it such as iterators being part of libcore so i don't need reactive extensions.

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

  • Why am I writing a Rust compiler in C?

    4 projects | news.ycombinator.com | 25 Aug 2024
  • How hard would it be to port the Rust toolchain to a new non-POSIX OS written in Rust and get it to host its own development? What would that process entail?

    3 projects | /r/rust | 5 Jul 2023
  • Is there any other language that has something crucial that Rust hasn't? Minus libraries.

    5 projects | /r/rust | 30 Dec 2021
  • Librsvg, Rust, and non-mainstream architectures

    5 projects | /r/rust | 26 Feb 2021
  • Rust Needs an Official Specification

    1 project | news.ycombinator.com | 12 Nov 2024

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