)]}'
{
  "commit": "abb9af83bc223eca0ffffce246ed551f2fcd11e1",
  "tree": "ca39464f3cb68c86c6b792220c907e15e63c4273",
  "parents": [
    "3a7dfdb984434a4b4beef947b2e49602c557c0de"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Mon Mar 06 14:25:39 2023 -0500"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Mon Mar 06 20:05:26 2023 +0000"
  },
  "message": "Work around a NASM bug\n\nI did not have \"find a bug in the assembler\" on my bingo card today, but\nhere we are.\n\nNASM 2.15, prior to 2.15.04, has a bug where, if a section that already\nexists is referenced again with alignment qualifiers, it incorrect adds\npadding and mangles the output. See\nhttps://bugzilla.nasm.us/show_bug.cgi?id\u003d3392701.\n\nWork around this by suppressing the perlasm-emitted qualifiers the\nsecond time a section is emitted. We likely don\u0027t need these qualifiers\nbecause, for all sections we care about, NASM\u0027s defaults are fine, but\nperlasm tries to align .text more aggressively than the default, so let\nit do that.\n\nBug: chromium:1422018\nChange-Id: Iade5702c139b70772d4957a83c8f9be86c8af97c\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/57825\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b8802c586affcbb68d4be01de8335530f7b2de95",
      "old_mode": 33261,
      "old_path": "crypto/perlasm/x86_64-xlate.pl",
      "new_id": "16a7846835f1a9b23d3e4e32c35b77c444d281df",
      "new_mode": 33261,
      "new_path": "crypto/perlasm/x86_64-xlate.pl"
    }
  ]
}