You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: "2019-10-31 Compiler Team Triage Meeting"
6
+
team: the compiler team <https://www.rust-lang.org/governance/teams/compiler>
7
+
---
8
+
9
+
The compiler team had our weekly triage meeting on 2019-10-31.
10
+
You can find the [minutes](https://rust-lang.github.io/compiler-team/minutes/triage-meeting/2019-10-31/) on the [compiler-team](https://github.com/rust-lang/compiler-team) repository.
11
+
Each week, we have general announcements from the team followed by check-ins from two of the compiler team working groups.
- PGO is available in the stable compiler. Docs are in the rustc-guide and the rustc-book
24
+
25
+
- Unfortunately we don't observe significant performance gains from applying it (except for tiny synthetic test cases).
26
+
27
+
-[@michaelwoerister] asked for people to try PGO on irlo but haven't gotten a lot of feedback.
28
+
29
+
- There is one interesting theory that Rust doesn't profit as much as C++ because it defaults to having fewer compilation units and thus can make better inlining decisions in the non-PGO case.
30
+
31
+
- The working group will probably wind down as [@michaelwoerister] don't have time to pursue further and there are no actual known issues in the implementation.
32
+
33
+
[Link to full discussion](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/weekly.20meeting.202019-10-31.20.2354818/near/179539153)
[Link to full discussion](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/weekly.20meeting.202019-10-31.20.2354818/near/179539371)
0 commit comments