Topic: Organizational Planning 
Audience
compiler team
Key People
probably just about everyone on compiler team
When
Thursday, 11:00-13:00
Where
Gainsboro
Meeting Style
Discussion
Deliverables

Homework to do before meeting
  • None
Agenda
  • Major Problems for 2019
  • Compiler Performance
  • RLS Completions
  • Too hard to do things (“technical debt”)
  • Too hard to find people to do things (“organizational debt”)
  • No “journeyperson” onboarding path
  • Code generation performance gaps
  • Major Themes
  • Parallelize the compiler
  • Improving existing incremental structure?
  • MIR Optimization
  • Working Group Structure / Journeypeople
  • RLS 2.0
  • Library-ification
  • Working Groups
  • Concept: Very minimal, repository w/ info, Zulip stream and/or contact info
  • Steering meeting w/ periodic updates
  • Question / Broadcast channel:
  • Compiler Performance working group — broadcast mechanism to reach people
  • Triage status:
  • Backlog of RFC features? Moving towards stability?
  • Working Group Proposal
  • “Meta” — nmatsakis — org. debt
  • feature lifecycle
  • RLS 2.0 (“the experiment”) — completions, compiler perf

  • Parallelizing the Compiler — compiler perf @Michael W
  • Zoxc, mw
  • MIR Optimization — code gen, compiler perf @Oli N
  • oli, nox, eddyb
  • Traits -- libraryifiation / tech debt / compiler perf
  • aturon, ..
  • Polonius — libraryifiation / tech debt / compiler perf
  • nmatsakis
  • Profile-Guided Optimization (PGO) — code gen @Michael W
  • mw
  • Cross-lang inlining / incremental thinLTO — code gen
  • mw
  • Symbol mangling — none of the above => EDIT: actually technical debt