fix and clarify llvm bugfix policy (#1611)

This commit is contained in:
Tshepang Mbambo 2023-02-18 13:46:21 +02:00 committed by GitHub
parent 6f536e44bc
commit 8715e8f6e8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions

View File

@ -2,7 +2,7 @@
<!-- toc --> <!-- 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, There is no formal policy about when to update LLVM or what it can be updated to,
but a few guidelines are applied: 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: 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 * A bug could have been fixed!
them upstream in LLVM. We'll want to pull fixes back to the compiler itself as Note that if we are the ones who fixed such a bug,
they're merged upstream. we prefer to upstream it, then pull it back for use by rustc.
* LLVM itself may have a new release. * LLVM itself may have a new release.