about summary refs log tree commit diff
path: root/src/doc/rustc-dev-guide
diff options
context:
space:
mode:
authorTshepang Mbambo <tshepang@gmail.com>2023-02-18 13:46:21 +0200
committerGitHub <noreply@github.com>2023-02-18 20:46:21 +0900
commit4b8cc1b285fc35a7bab5198e48f8d119453ee2f2 (patch)
tree5517df3b8d0d20b8989ecbe29d05a26de967145d /src/doc/rustc-dev-guide
parenta93cf5fb3079a3b55ca747799d3c64aeea7587b2 (diff)
downloadrust-4b8cc1b285fc35a7bab5198e48f8d119453ee2f2.tar.gz
rust-4b8cc1b285fc35a7bab5198e48f8d119453ee2f2.zip
fix and clarify llvm bugfix policy (#1611)
Diffstat (limited to 'src/doc/rustc-dev-guide')
-rw-r--r--src/doc/rustc-dev-guide/src/backend/updating-llvm.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/src/doc/rustc-dev-guide/src/backend/updating-llvm.md b/src/doc/rustc-dev-guide/src/backend/updating-llvm.md
index 38fbb2e440f..ce0890491c0 100644
--- a/src/doc/rustc-dev-guide/src/backend/updating-llvm.md
+++ b/src/doc/rustc-dev-guide/src/backend/updating-llvm.md
@@ -2,7 +2,7 @@
 
 <!-- toc -->
 
-<!-- date-check: Aug 2022 -->
+<!-- date-check: Feb 2023 -->
 There is no formal policy about when to update LLVM or what it can be updated to,
 but a few guidelines are applied:
 
@@ -16,9 +16,9 @@ but a few guidelines are applied:
 
 There are two reasons we would want to update LLVM:
 
-* A bug could have been fixed! Often we find bugs in the compiler and fix
-  them upstream in LLVM. We'll want to pull fixes back to the compiler itself as
-  they're merged upstream.
+* A bug could have been fixed!
+  Note that if we are the ones who fixed such a bug,
+  we prefer to upstream it, then pull it back for use by rustc.
 
 * LLVM itself may have a new release.