)]}'
{
  "commit": "fabb73d1bb833f7da40971757b51635cda9274e8",
  "tree": "b7c7907e4d608bddc003e8fe289d5fe7002e7534",
  "parents": [
    "77b07380deafa490b4c2da3c4d1661060b5319c9"
  ],
  "author": {
    "name": "Jan Beulich",
    "email": "jbeulich@suse.com",
    "time": "Fri Mar 01 09:25:59 2024 +0100"
  },
  "committer": {
    "name": "Jan Beulich",
    "email": "jbeulich@suse.com",
    "time": "Fri Mar 01 09:25:59 2024 +0100"
  },
  "message": "x86: adjust which Dwarf2 register numbers to use\n\nConsumers can\u0027t know which execution mode is in effect for a certain\npiece of code; they can only go from object file properties. Hence which\nregister numbers to encode ought to depend solely on object file type.\n\nIn tc_x86_frame_initial_instructions() do away with parsing a register\nname: We have a symbolic constant already for the 64-bit case, and the\n32-bit number isn\u0027t going to change either. Said constant\u0027s definition\nneeds moving, though, to be available also for non-ELF. While moving\nalso adjust the comment to clarify that it\u0027s applicable to 64-bit mode\nonly.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "93de0b6192c24439d03973efd315779e4c49be10",
      "old_mode": 33188,
      "old_path": "gas/config/tc-i386.c",
      "new_id": "fecb25a3fe2fe9e8bc2a97a338fbc3e089ca98a4",
      "new_mode": 33188,
      "new_path": "gas/config/tc-i386.c"
    },
    {
      "type": "modify",
      "old_id": "b93799a3b48cfe307b14aa6c2ae930f47f4d7e8c",
      "old_mode": 33188,
      "old_path": "gas/config/tc-i386.h",
      "new_id": "7aae7a33dc1478d4893af36d54b72dd7e8cf0ace",
      "new_mode": 33188,
      "new_path": "gas/config/tc-i386.h"
    }
  ]
}
