From 40d0b76e3bff17accc1e43cfd436198f5f62da59 Mon Sep 17 00:00:00 2001 From: Niko Matsakis Date: Thu, 10 Oct 2019 14:28:02 -0400 Subject: [PATCH 1/4] announce LLVM ICE-breaker group --- .../2019-10-10-LLVM-ICE-breakers.md | 39 +++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 posts/inside-rust/2019-10-10-LLVM-ICE-breakers.md diff --git a/posts/inside-rust/2019-10-10-LLVM-ICE-breakers.md b/posts/inside-rust/2019-10-10-LLVM-ICE-breakers.md new file mode 100644 index 000000000..7f27da72d --- /dev/null +++ b/posts/inside-rust/2019-10-10-LLVM-ICE-breakers.md @@ -0,0 +1,39 @@ +--- +layout: post +title: "Announcing the LLVM ICE-breaker group" +author: Niko Matsakis +description: "A new blog where the Rust team can post updates on the latest developments" +team: the compiler team +--- + +Today I'm announcing a new experiment in the compiler team, the **LLVM ICE-breaker group**. If you're familiar with LLVM and would like to contribute to rustc -- but without taking on a large commitment -- then the LLVM ICE-breaker group might well be for you! + +### What is the LLVM ICE-breaker group? + +At its heart, the LLVM ICE-breaker group is just a list of people who would like to be notified when we come across LLVM bugs. You can add yourself to this list very easily -- just [open a PR]! Once you do so, you'll start to get pings when we come across suitable bugs. If you have some time, maybe you can fix one of them, or at least offer some words of wisdom to help somebody else figure out what's going on. + +[open a PR]: https://rust-lang.github.io/rustc-guide/ice-breaker/about.html#join + +There are a few other things associated with the group too, however. For example, we've got a [guide] that offers some tips for how to fix LLVM-related bugs and may help you get started (particularly if you're not that familiar with rustc). + +[guide]: https://rust-lang.github.io/rustc-guide/ice-breaker/llvm.html + +### What kind of bugs are we talking about? + +The goal is to identify "self-contained" bugs that are unlikely to require large-scale compiler refactorings or to get entangled in other big projects. + +### What's with the name ICE-breaker anyway? + +An "ICE" is an "internal compiler error". It actually refers specifically to the case where the compiler panics (which tends to be an easy sort of bug to fix). In fact, very few LLVM bugs cause real ICEs, but the name was too good to pass up. + +But of course we also hope that these ICE-breaker groups can help people to get more acquainted with hacking on rustc; to ["break the ice"], if you will (ha! I kill me). + +["break the ice"]: https://en.wiktionary.org/wiki/break_the_ice + +### Will there be more ICE-breaker groups? + +I certainly hope so! As I mentioned before, this is an experiment, but presuming that it works out well we fully intend to create more ICE-breaker groups. + +### So how do I sign up again? + +Easy! Just [open a PR]! From f448f4510383c558639d034d111c47b8eaf3972e Mon Sep 17 00:00:00 2001 From: Niko Matsakis Date: Tue, 22 Oct 2019 12:55:00 -0400 Subject: [PATCH 2/4] add some notes about "who should join" --- posts/inside-rust/2019-10-10-LLVM-ICE-breakers.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/posts/inside-rust/2019-10-10-LLVM-ICE-breakers.md b/posts/inside-rust/2019-10-10-LLVM-ICE-breakers.md index 7f27da72d..e64a2b3ac 100644 --- a/posts/inside-rust/2019-10-10-LLVM-ICE-breakers.md +++ b/posts/inside-rust/2019-10-10-LLVM-ICE-breakers.md @@ -22,6 +22,15 @@ There are a few other things associated with the group too, however. For example The goal is to identify "self-contained" bugs that are unlikely to require large-scale compiler refactorings or to get entangled in other big projects. +### Who should join? + +This group is a great fit for anyone who is familiar with LLVM and who would like to learn more about Rust or to get more involved in the Rust project. Even if you don't have time to open PRs against rustc, there are many other ways to help: + +* identifying open LLVM bugs that we may be running into; +* reducing Rust sources to minimal reducers; +* reducing LLVM IR to minimal problem cases; +* and so forth. + ### What's with the name ICE-breaker anyway? An "ICE" is an "internal compiler error". It actually refers specifically to the case where the compiler panics (which tends to be an easy sort of bug to fix). In fact, very few LLVM bugs cause real ICEs, but the name was too good to pass up. From d008a00855dfc62843c8d73703233fc044d29bee Mon Sep 17 00:00:00 2001 From: Niko Matsakis Date: Tue, 22 Oct 2019 12:55:30 -0400 Subject: [PATCH 3/4] rename to the current date --- ...10-10-LLVM-ICE-breakers.md => 2019-10-22-LLVM-ICE-breakers.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename posts/inside-rust/{2019-10-10-LLVM-ICE-breakers.md => 2019-10-22-LLVM-ICE-breakers.md} (100%) diff --git a/posts/inside-rust/2019-10-10-LLVM-ICE-breakers.md b/posts/inside-rust/2019-10-22-LLVM-ICE-breakers.md similarity index 100% rename from posts/inside-rust/2019-10-10-LLVM-ICE-breakers.md rename to posts/inside-rust/2019-10-22-LLVM-ICE-breakers.md From b05ba838eb3420f73196630eeca94a5e0dffedf8 Mon Sep 17 00:00:00 2001 From: Niko Matsakis Date: Tue, 22 Oct 2019 12:56:34 -0400 Subject: [PATCH 4/4] encourage learners --- posts/inside-rust/2019-10-22-LLVM-ICE-breakers.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/posts/inside-rust/2019-10-22-LLVM-ICE-breakers.md b/posts/inside-rust/2019-10-22-LLVM-ICE-breakers.md index e64a2b3ac..9740d2ecc 100644 --- a/posts/inside-rust/2019-10-22-LLVM-ICE-breakers.md +++ b/posts/inside-rust/2019-10-22-LLVM-ICE-breakers.md @@ -31,6 +31,8 @@ This group is a great fit for anyone who is familiar with LLVM and who would lik * reducing LLVM IR to minimal problem cases; * and so forth. +(For that matter, feel freeo to join the group even if you're *not* all that familiar with LLVM -- no better way to learn!) + ### What's with the name ICE-breaker anyway? An "ICE" is an "internal compiler error". It actually refers specifically to the case where the compiler panics (which tends to be an easy sort of bug to fix). In fact, very few LLVM bugs cause real ICEs, but the name was too good to pass up.