databend VS rustc_codegen_gcc

Databend vs. Snowflake: https://github.com/datafuselabs/databend/issues/13059

Indeed, under a pay-as-you-go model, if there's a lack of precise control over the warehouse, such as a 10-minute suspension, it could lead to significant waste. This is because most queries might only take a few seconds, and the rest of the time is wasted. If you find Snowflake expensive, consider Databend. It's an open-source, cost-efficient alternative to Snowflake, and it maintains a consistent product experience with Snowflake.

Open-source: https://github.com/datafuselabs/databend

They're advertising as an open source direct competitor with Snowflake, with the ability to store data in parquet files. Github repo (5.6k stars) here.

Databend has recently introduced an SQL function that generates SQL statements from natural language. This feature can significantly reduce the time required for writing and debugging SQL statements.

Hi, we used to use sqlparser in [Databend](https://github.com/datafuselabs/databend). But at last we decide to write our own sqlparser using nom-rule.

Link to Github: https://github.com/datafuselabs/databend

Alternatively, there's another initiative called codegen_gcc which is about using GCC as a backend for the rustc compiler. It's (much) more advanced in Rust support, but I am not sure how easy it would be to use a modified libgccjit from there.

In addition to what others have said about platform support, Rust is also on its way to gaining more platform support through rustc_codegen_gcc, the GCC codegen backend for rustc, as an alternative to the LLVM backend. That means many of the platforms GCC supports will suddenly become available with Rust.

Yeah, rustc_codegen_gcc is a GCC backend for rustc, and its making a lot of good regular progress.

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.

Fixing unwinding in release mode is still ungoing. I could use some help here, so anyone with some understanding of unwinding, landing pads or GCC, please come on this issue to discuss this.

Additionally, there is gcc codegen for rustc (https://github.com/rust-lang/rustc_codegen_gcc), which is not a compiler per se, but an alternative code generator, with more architectures supported and other nice things. It's also coming along, but there's still a lot of work to do there too. There's also Cranelift codegen (https://github.com/bjorn3/rustc_codegen_cranelift), which is designed to make debug builds faster, but this is not as exciting/useful as the other 2.

Good idea. I added the tag "help wanted" to the issue.

Also, there are indeed ABI issues, e.g. for 128-bit integers and NaN.

I'm excited about both the backend & the frontend.

There is also a project for rustc to use GCC instead of LLVM for codegen.

https://github.com/rust-lang/rustc_codegen_gcc