)]}'
{
  "commit": "8162cf582b4161cfaecbfd32b228697f198fd661",
  "tree": "47e86d1cb77a276c5b615f2f2d9c1dbb590dae32",
  "parents": [
    "b954122bbe6c4a244c511a9a168c6d5438d8f58f",
    "405214dd924835aa43367565dbacaf69609c2e4b"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Thu May 21 12:21:45 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Thu May 21 12:21:45 2026 +0200"
  },
  "message": "Rollup merge of #156242 - Jamesbarford:feat/remove-alwaysinline+target-feature, r\u003dRalfJung,saethlin\n\nRemove unsound `target_feature_inline_always` feature\n\n## Summary\n- Remove `target_feature_inline_always`\n- Update stdarch generators to only use `#[inline]` \u0026 regenerate stdarch.\n\n## Why?\nSuccinctly; the feature relies on LLVMs `AlwaysInlinerPass()` running before LLVMs heuristic based inliner pass. Which is not a basis for sound code.\n\nThis has been discussed in [the tracking issue](https://github.com/rust-lang/rust/issues/145574).\n\nIf the ordering of the passes were to change, of which they have in the past, it is very possible we could inline functions across callsites with mismatching target features leading to unsound code. Checks proposed in; https://github.com/rust-lang/rust/pull/155426 would only take into account caller -\u003e callee which is not enough to guard against possibly of generating unsound code if the pass ordering were to change.\n\nThere doesn\u0027t seem to be a way, presently, this this mechanism to provide soundness guarantees nor does it seem like `AlwaysInlinerPass()` is a desired feature of LLVM, which this feature relies on.\n\nr? @RalfJung\n",
  "tree_diff": []
}