Did you know that macOS has a secret setting that can make Rust builds faster? It can also make Rust tests faster. It probably even has similar effects for other compiled languages such as C, C++, Go, and Swift. It sounds crazy, but read on…| Nicholas Nethercote
Be kind and be useful.| Nicholas Nethercote
If you are using #[derive(Arbitrary)] to fuzz your Rust code, update the Arbitrary crate to v1.4.2 to get some compile time reductions and possibly some fuzzing speed improvements.| Nicholas Nethercote
This post describes some performance work I have been doing recently on rustc. I spent several weeks on a particular problem with only a small amount of success. I hope a write-up will be interesting and educational, and may even lead to suggestions that make things better. The post is aimed at readers with some familiarity with compilers.| Nicholas Nethercote
For the past 3.75 years I have been fortunate to work on Futurewei’s Rust team, where I had enormous freedom to “make Rust better” however I see fit. It has been the highlight of my career and I am grateful to Sid Askary and other Futurewei folks that helped make it happen.| Nicholas Nethercote
Rust’s proc macros are powerful but tricky, and have some compile-time costs. This post is about a new tool to help quantify and reduce some of those costs.| Nicholas Nethercote
Build Configuration| nnethercote.github.io
It has been two months since my last post on the Rust compiler’s performance. Time for a small update.| Nicholas Nethercote
My house is now free from the direct burning of fossil fuels. Here’s how I did it.| Nicholas Nethercote
It has been just over a year since my last update on the Rust compiler’s performance. Let’s get into it. The information about metrics at the top of this post still applies.| Nicholas Nethercote
Sometimes I pick a crate in the Rust compiler and read through its code to learn about it and find things that I can improve. Often the improvements are small, but sometimes they snowball.| Nicholas Nethercote
I recently joined the general code review rotation for the Rust compiler, which increased the number of reviews I do. This post describes my experience, and contains some thoughts about reviewing in general.| Nicholas Nethercote
Welcome to the fifteenth post in my long-running “How to speed up the Rust compiler” series, and the first in 2023.| Nicholas Nethercote
It has been over six months since my last update on the Rust compiler’s performance. Time for an update.| Nicholas Nethercote
It has been five months since my last general update on the Rust compiler’s performance. Let’s see what has happened in that time.| Nicholas Nethercote
Last week I requested help with some data analysis of the Rust compiler.| Nicholas Nethercote
Update: see the follow-up post for responses and updated data sets.| Nicholas Nethercote
Valgrind 3.21 was released last week. The release announcement has the full details of the changes.| Nicholas Nethercote
It’s time to look at some of the progress on Rust compiler speed made since my last post in July.| Nicholas Nethercote
It has been twenty years since Valgrind 1.0 was released.| Nicholas Nethercote
Let’s look at some of the progress on Rust compiler speed made since my last post. I will start with some important changes made by other people.| Nicholas Nethercote
Between 2016 and 2020 I wrote a series of blog posts called “How to speed up the Rust compiler”. These were mostly about my work on the Rust compiler, plus some updates on the progress on the Rust compiler’s speed in general.| Nicholas Nethercote