dneto, 11 days ago to llvm

So the thing about LLVM IR is, in reality it's a family of accidental and informally defined dialects. Every LLVM-based compiler for a particular machine target refines the input module down to its own idiosyncratic dialect.

Consequently there's way more latitude for confusion and bugs than you'd initially guess.

Try using an i65 type in an x86 backend. When I did that years ago it sailed right through and generated nonsense code.

#llvm #compilers

jbzfn, 12 days ago to programming

⏳ Am I too old to create a popular programming language?

"Is it too late to create a popular programming language after age 40? Let's find out!"

https://pldb.io/posts/age.html

#PLT #Programming #Compilers

nogweii, 14 days ago to rust

Supporting LTO in Rust seems really complicated. Reading pacman discussions, and issues in the ring crate. Weird things that different compiler toolchains do, and they all do slightly different things. #rust #compilers

amoroso, 14 days ago to random

A list of compiler optimizations with descriptions and code snippets.

The entries are concise, clear, and with short, easy to understand snippets. A great example of algorithm documentation.

https://compileroptimizations.com/index.html

#compilers #ProgLang

folkertdev, 27 days ago to rust

My first concrete result of #RustNL: zlib-rs now runs with the #rust cranelift backend

This required implementing some intrinsics that the cranelift backend didn't yet support

https://github.com/rust-lang/rustc_codegen_cranelift/pull/1491
https://github.com/rust-lang/rustc_codegen_cranelift/pull/1488

With some help from bjorn3 this was reasonably straightforward. I think the PRs are good templates for of someone wanted to work on a real compiler and implement further SIMD functionality. This issue lists some missing intrinsics

https://github.com/rust-lang/rustc_codegen_cranelift/issues/1419

#compilers