)]}'
{
  "commit": "ecbc5c4f9059dd483cf8b0705cbd4e2e9606aad5",
  "tree": "43827ec45e63690388b13e05cf33cfa74bddcf66",
  "parents": [
    "c22a74728313ee35f6bf143238d42e2eca9ed020"
  ],
  "author": {
    "name": "Felix Willgerodt",
    "email": "felix.willgerodt@intel.com",
    "time": "Mon Feb 13 11:02:23 2023 +0100"
  },
  "committer": {
    "name": "Felix Willgerodt",
    "email": "felix.willgerodt@intel.com",
    "time": "Wed Feb 15 09:51:28 2023 +0100"
  },
  "message": "gdb, fortran: Fix quad floating-point type for ifort compiler.\n\nI fixed this a while ago for ifx, one of the two Intel compilers, in\n8d624a9d8050ca96e154215c7858ac5c2d8b0b19.\n\nApparently I missed that the older ifort Intel compiler actually emits\nslightly different debug info again:\n\n0x0000007a:   DW_TAG_base_type\n                DW_AT_byte_size\t(0x20)\n                DW_AT_encoding\t(DW_ATE_complex_float)\n                DW_AT_name\t(\"COMPLEX(16)\")\n\n0x00000081:   DW_TAG_base_type\n                DW_AT_byte_size\t(0x10)\n                DW_AT_encoding\t(DW_ATE_float)\n                DW_AT_name\t(\"REAL(16)\")\n\nThis fixes two failures in gdb.fortran/complex.exp with ifort.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "da4950ac259f2eec4d36940bbf5393f41e8dc83c",
      "old_mode": 33188,
      "old_path": "gdb/i386-tdep.c",
      "new_id": "acf22dba98ded0a027d794e3f967479c5e88598d",
      "new_mode": 33188,
      "new_path": "gdb/i386-tdep.c"
    }
  ]
}