)]}'
{
  "commit": "0038be43830c898cf5a2f089dfd6ba467a4040c8",
  "tree": "6f56fb75925922cd6faf9d0f85871f480eeb0ed1",
  "parents": [
    "d46794756740de156be48134653aeb49df6bd5f8",
    "1287aebd1b35af43aa643d75f3ea9366ae39ce04"
  ],
  "author": {
    "name": "bors",
    "email": "bors@rust-lang.org",
    "time": "Fri Sep 18 04:48:34 2026 +0000"
  },
  "committer": {
    "name": "bors",
    "email": "bors@rust-lang.org",
    "time": "Fri Sep 18 04:48:34 2026 +0000"
  },
  "message": "Auto merge of #161583 - RalfJung:x86-sse-abi, r\u003dnikic\n\nx86: on targets that requires SSE, use those registers for ABI\n\n\r\n\r\nNow that https://github.com/llvm/llvm-project/issues/142321 is fixed, we can use the vector ABI without re-introducing https://github.com/rust-lang/rust/issues/139029. So this effectively reverts https://github.com/rust-lang/rust/pull/141309.\r\n\r\nSince this means we are relying on the SSE target feature for the Rust ABI, we also need to turn the ABI target feature check into a hard error. If we don\u0027t do that, we\u0027ll get post-mono errors in some situations and plain miscompilations in others.\r\n\r\nAlso this will cause performance regressions on LLVM 22 and 21 as those don\u0027t have the fix for  https://github.com/llvm/llvm-project/issues/142321. IMO that\u0027s fine. Programs will do the right thing, they will just be a bit slower due to https://github.com/rust-lang/rust/issues/139029.\r\n\r\nr? @nikic \r\nCc @tgross35 ",
  "tree_diff": []
}