From b0266f26f17be0cea8d0ecd56186dbd2c210f790 Mon Sep 17 00:00:00 2001 From: Tshepang Mbambo Date: Sun, 30 Jul 2023 14:01:23 +0200 Subject: [PATCH 1/3] llvm 16 is now supported --- src/backend/updating-llvm.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/backend/updating-llvm.md b/src/backend/updating-llvm.md index 08af10f89..028747bd5 100644 --- a/src/backend/updating-llvm.md +++ b/src/backend/updating-llvm.md @@ -139,6 +139,7 @@ so let's go through each in detail. > - [LLVM 13](https://github.com/rust-lang/rust/pull/87570) > - [LLVM 14](https://github.com/rust-lang/rust/pull/93577) > - [LLVM 15](https://github.com/rust-lang/rust/pull/99464) + > - [LLVM 16](https://github.com/rust-lang/rust/pull/109474) Note that sometimes it's easiest to land [`llvm-wrapper`] compatibility as a PR before actually updating `src/llvm-project`. From c57a5b4a32bfed2bab27c8751b86656392fcc33d Mon Sep 17 00:00:00 2001 From: Tshepang Mbambo Date: Sun, 30 Jul 2023 14:02:11 +0200 Subject: [PATCH 2/3] llvm coverage mapping format is still at v6 --- src/llvm-coverage-instrumentation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/llvm-coverage-instrumentation.md b/src/llvm-coverage-instrumentation.md index 2b1677ef4..297000915 100644 --- a/src/llvm-coverage-instrumentation.md +++ b/src/llvm-coverage-instrumentation.md @@ -223,7 +223,7 @@ details of the [_LLVM Coverage Mapping Format_][coverage-mapping-format] (Version 6).[^llvm-and-covmap-versions] [^llvm-and-covmap-versions]: -The Rust compiler (as of Feb 2023) supports _LLVM Coverage Mapping Format_ 6. +The Rust compiler (as of Jul 2023) supports _LLVM Coverage Mapping Format_ 6. The Rust compiler will automatically use the most up-to-date coverage mapping format version that is compatible with the compiler's built-in version of LLVM. From fa7419d416e989376f6c8e59089a0763f485b819 Mon Sep 17 00:00:00 2001 From: Tshepang Mbambo Date: Sun, 30 Jul 2023 14:08:04 +0200 Subject: [PATCH 3/3] policy and practice have not changed, looking at zulip history --- src/backend/updating-llvm.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/backend/updating-llvm.md b/src/backend/updating-llvm.md index 028747bd5..dd16b1e28 100644 --- a/src/backend/updating-llvm.md +++ b/src/backend/updating-llvm.md @@ -2,7 +2,7 @@ - + There is no formal policy about when to update LLVM or what it can be updated to, but a few guidelines are applied: @@ -52,7 +52,7 @@ An example PR: ## New LLVM Release Updates - + Unlike bugfixes, updating to a new release of LLVM typically requires a lot more work.