)]}'
{
  "commit": "b6839f4d0e2bd63b960bbff8619c6fdea27d81e5",
  "tree": "86d756e0edaddb043cac910544472d6b34935b7a",
  "parents": [
    "421875f8d2bbb9a9a47db179092a3266b87106d4",
    "f14f0c11e6a62eec303bcbee2c096641acc5bb0a"
  ],
  "author": {
    "name": "bors",
    "email": "bors@rust-lang.org",
    "time": "Fri Jul 17 19:57:24 2026 +0000"
  },
  "committer": {
    "name": "bors",
    "email": "bors@rust-lang.org",
    "time": "Fri Jul 17 19:57:24 2026 +0000"
  },
  "message": "Auto merge of #159091 - Kobzol:bootstrap-pgo-rustdoc, r\u003dMark-Simulacrum\n\nUse PGO for rustdoc\n\n\r\n\r\nThis PR extends the recently added support for configuring PGO options per component in bootstrap to support `rustdoc` and enables PGO training on `Doc` benchmarks.\r\n\r\nWe build PGO-instrumented rustc and rustdoc together.\r\n\r\nI tested two variants:\r\n- Run all rustc benchmarks *also* on `Doc` rustc-perf profiles, and then use the same merged PGO profile to optimize both rustc and rustdoc\r\n  - https://github.com/rust-lang/rust/pull/159091#issuecomment-4938762762\r\n- Run rustc benchmarks separately, and generate the rustc PGO profile from that, same as before. Then run *only* `Doc` benchmarks, and generate a rustdoc PGO profile from that, and use that to optimize rustdoc (note that here we run the `Doc` benchmarks using a PGO instrumented rustc too, so the profiles will include PGO data from librustc_driver.so).\r\n  - https://github.com/rust-lang/rust/pull/159091#issuecomment-4945458162\r\n\r\nI think that the second reason is slightly better, and produces better results (and less rustc regressions).\r\n\r\nGathering the rustdoc PGO profiles takes barely over a minute, I don\u0027t think that this should have a large effect on the duration of the `dist-x86_64-linux` job.\r\n\r\ntry-job: dist-x86_64-msvc\r\ntry-job: dist-x86_64-linux",
  "tree_diff": []
}