)]}'
{
  "commit": "7eccd2e407890a554ffc64d015ba82b7fdf941c4",
  "tree": "6fd7a2114b8e65a0e5fa229143a89c922516b9f0",
  "parents": [
    "a8551849716c2b29e59547212e3aa69b8f4e2ad8"
  ],
  "author": {
    "name": "Tom Tromey",
    "email": "tromey@adacore.com",
    "time": "Mon Aug 26 12:54:17 2024 -0600"
  },
  "committer": {
    "name": "Tom Tromey",
    "email": "tromey@adacore.com",
    "time": "Thu Mar 06 14:17:17 2025 -0700"
  },
  "message": "Compare unqualified names in ada_identical_enum_types_p\n\nWith the coming changes to GNAT, gdb must compare the unqualified\nnames of two enum types.\n\nCurrently, GNAT will fully-qualify enumeration constant names, so for\ninstance one might see \"enum_with_gap__lit4\" as the name.\n\nGNAT also may emit a copy of an enumeration type when a newtype is\ninvolved.  E.g., in the arr_acc_idx_w_gap.exp test case, this can\noccur for the base type of this subtype:\n\n   type Enum_Subrange is new Enum_With_Gaps range Lit1 .. Lit3;\n\n(Note that the base type of this subrange is anonymous.)\n\nWith some forthcoming changes to GNAT, these names will no longer be\nqualified -- and because the newtype is anonymous, they can\u0027t be\nidentically qualified.  But, in gdb we still want \"lit4\" to resolve\nwithout ambiguity in this scenario.\n\nThe fix is to change ada_identical_enum_types_p to compare unqualified\nenum names.  This will work correctly with both variants of the\ncompiler, and with -fgnat-encodings\u003dall as well.\n\n\n\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d26139b802ffec4b83662ce647be1fcacad95297",
      "old_mode": 33188,
      "old_path": "gdb/ada-lang.c",
      "new_id": "ab92f6473ac32f9915bf4fd894867da3e5e50db9",
      "new_mode": 33188,
      "new_path": "gdb/ada-lang.c"
    }
  ]
}