)]}'
{
  "commit": "80f74433dbd201f6cf1eabf24820acf08993d110",
  "tree": "d2f6a4c56687d4a4a1bbf36b0dd639943d6e501a",
  "parents": [
    "07d97873828a24fe06c6eae2feff45f10518f089",
    "a5f012576cf0dab7439050696f1c0b7795b3f3aa"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Tue Aug 25 18:00:08 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Aug 25 18:00:08 2026 +0200"
  },
  "message": "Rollup merge of #161522 - folkertdev:gcc-fma16-correctly-rounded, r\u003dtgross35\n\ntest `f16::mul_add` not double-rounding the result\n\ntest the precision of `f16::mul_add`. The semantics of `mul_add` are that there should only be one rounding of the final result back into the storage type, i.e. the intermediate result of the multiplication should not be rounded.\n\nA naive implementation of `f16::mul_add` as `f32::mul_add(a as f32, b as f32, c as f32) as f16` has insufficient precision, see https://github.com/llvm/llvm-project/issues/98389.\n\nOur `rustc_codegen_gcc` backend still used the `f32` approach, this PR changes it to instead (implicitly) use the fallback body from `core`, which uses `f64::mul_add` so that the result is correctly rounded.\n",
  "tree_diff": []
}