)]}'
{
  "commit": "8ec0547e24972e7cf23e8096d0e8db3d2c44b45f",
  "tree": "f847030f288c7f51746e71bde7d02f852816f6f4",
  "parents": [
    "11f59ab65c277af9d354d158cc996dbbd3d43a2b"
  ],
  "author": {
    "name": "Alex Coplan",
    "email": "alex.coplan@arm.com",
    "time": "Fri Jul 17 18:40:52 2026 +0100"
  },
  "committer": {
    "name": "Alex Coplan",
    "email": "alex.coplan@arm.com",
    "time": "Mon Jul 20 15:36:13 2026 +0100"
  },
  "message": "aarch64: Fix up TME deprecation warning\n\nThis is a follow-up patch to Richard E\u0027s r17-2498-g17f084306c68c4 (#186\non the Forge).  As Alice pointed out in her review:\nhttps://gcc.gnu.org/pipermail/gcc-patches/2026-July/724391.html\nthe original patch missed things like +memtag+tme due to the string\nparsing approach.  This instead just inspects the parsed feature flags\nfrom aarch64_parse_extension to determine whether to warn in the target\nattribute/pragma case.\n\n+tme on the command line is handled as per Richard\u0027s original patch (no\nchange there).\n\ngcc/ChangeLog:\n\n\t* config/aarch64/aarch64.cc (aarch64_handle_attr_isa_flags):\n\tWarn if +tme is enabled by the target attribute/pragma, relying\n\ton the feature flags from aarch64_parse_extension.\n\t(aarch64_process_target_attr): Drop +tme warning based on custom\n\tstring parsing.\n\ngcc/testsuite/ChangeLog:\n\n\t* gcc.target/aarch64/deprecate-tme.c: New test.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "40b68709dbb14c5177cb2fdf95a8f41114afcdbf",
      "old_mode": 33188,
      "old_path": "gcc/config/aarch64/aarch64.cc",
      "new_id": "61562c94a5530e77d3dc43d95e5ad42d50138392",
      "new_mode": 33188,
      "new_path": "gcc/config/aarch64/aarch64.cc"
    },
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "b190c4d2c2115aa9528bdb9bb268894b7b0c8bf9",
      "new_mode": 33188,
      "new_path": "gcc/testsuite/gcc.target/aarch64/deprecate-tme.c"
    }
  ]
}