)]}'
{
  "commit": "124c16e0de934595dfcdb0845cb39d2bcb8b970d",
  "tree": "4a7f014733a2401860d07294750663f8e736f6e7",
  "parents": [
    "c656540d6467dee1381f0cbd882412d6bd1cd5ae",
    "91defaa1213e86c76fb7c4d0ab858658ace3deff"
  ],
  "author": {
    "name": "bors",
    "email": "bors@rust-lang.org",
    "time": "Fri Aug 21 21:36:33 2026 +0000"
  },
  "committer": {
    "name": "bors",
    "email": "bors@rust-lang.org",
    "time": "Fri Aug 21 21:36:33 2026 +0000"
  },
  "message": "Auto merge of #161260 - weihanglo:cc-1.4.3, r\u003dKobzol\n\nchore: bump to cc@1.4.3 for rustc_llvm and library\n\n\n\n### What is this?\r\n\r\nOld cc-rs derives this from the `-Clto` rustflag on its own.\r\n`cc@1.2.39` starts gating that behind `-Clinker-plugin-lto`,\r\nwhich bootstrap doesn\u0027t pass.\r\nTherefore,\r\nwe need to pass this flag explicitly to keep LTO mode\r\n\r\nPrevious efforts:\r\n\r\n* https://github.com/rust-lang/rust/pull/146186\r\n* https://github.com/rust-lang/rust/pull/155438\r\n\r\nI personally want this because of cc 1.3.0+ has the support of Cargo `-Ztrim-paths`,\r\nwhich helps what I am experimenting in \u003chttps://github.com/rust-lang/rust/pull/161049\u003e.\r\n\r\n### How to review\r\n\r\nCommit by commit. \r\n\r\nTo keep commits bisect-able,\r\nI added the first commit without cc bump.\r\nclang should be fine with duplicate `-flto` flags.\r\n\r\nOne thing I am not certain is whether we should probe `-flto` flag in this case,\r\nor just make this fail if `-flto` isn\u0027t supported.\r\n(I assume `-flto` is quote widely supported)\r\n\r\nr? Kobzol\r\n\r\n---\r\n\r\n🤖 **LLM disclosure:** I used LLM for the experiment of \u003chttps://github.com/rust-lang/rust/pull/161049\u003e, but not the bootstrap LTO change in this PR.\r\n\r\n\r\n",
  "tree_diff": []
}