File tree 2 files changed +4
-3
lines changed
2 files changed +4
-3
lines changed Original file line number Diff line number Diff line change 2
2
3
3
<!-- toc -->
4
4
5
- <!-- date-check: Feb 2023 -->
5
+ <!-- date-check: Jul 2023 -->
6
6
There is no formal policy about when to update LLVM or what it can be updated to,
7
7
but a few guidelines are applied:
8
8
@@ -52,7 +52,7 @@ An example PR:
52
52
53
53
## New LLVM Release Updates
54
54
55
- <!-- date-check: Aug 2022 -->
55
+ <!-- date-check: Jul 2023 -->
56
56
57
57
Unlike bugfixes,
58
58
updating to a new release of LLVM typically requires a lot more work.
@@ -139,6 +139,7 @@ so let's go through each in detail.
139
139
> - [ LLVM 13] ( https://github.com/rust-lang/rust/pull/87570 )
140
140
> - [ LLVM 14] ( https://github.com/rust-lang/rust/pull/93577 )
141
141
> - [ LLVM 15] ( https://github.com/rust-lang/rust/pull/99464 )
142
+ > - [ LLVM 16] ( https://github.com/rust-lang/rust/pull/109474 )
142
143
143
144
Note that sometimes it's easiest to land [ ` llvm-wrapper ` ] compatibility as a PR
144
145
before actually updating ` src/llvm-project ` .
Original file line number Diff line number Diff line change @@ -223,7 +223,7 @@ details of the [_LLVM Coverage Mapping Format_][coverage-mapping-format]
223
223
(Version 6 ). [^ llvm - and - covmap - versions ]
224
224
225
225
[^ llvm - and - covmap - versions ]:
226
- The Rust compiler (as of <! -- date - check : - -> Feb 2023 ) supports _LLVM Coverage Mapping Format_ 6 .
226
+ The Rust compiler (as of <! -- date - check : - -> Jul 2023 ) supports _LLVM Coverage Mapping Format_ 6 .
227
227
The Rust compiler will automatically use the most up- to- date coverage mapping format
228
228
version that is compatible with the compiler's built- in version of LLVM .
229
229
You can’t perform that action at this time.
0 commit comments