fix and clarify llvm bugfix policy (rust-lang#1611)

Kobzol · Feb 18, 2023 · f56de63 · f56de63
1 parent a1726bd
commit f56de63
Showing 1 changed file with 4 additions and 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
@@ -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.