)]}'
{
  "commit": "7fdd4fcee1c6698daa8eb5f52017e768b0771503",
  "tree": "d9707c26a835f1f2094aaeb8f4d4e710cc0811cd",
  "parents": [
    "b47a4f92de5c12ac8bdac57b0413e3e05d411832"
  ],
  "author": {
    "name": "Joseph Myers",
    "email": "joseph@codesourcery.com",
    "time": "Fri Sep 01 15:20:47 2023 +0000"
  },
  "committer": {
    "name": "Joseph Myers",
    "email": "joseph@codesourcery.com",
    "time": "Fri Sep 01 15:20:47 2023 +0000"
  },
  "message": "config: Fix host -rdynamic detection for build !\u003d host !\u003d target\n\n[Merge from GCC commit 4d9bc81a5d8d884dee7a7781fa4c1577a6c9681a.]\n\nThe GCC_ENABLE_PLUGINS configure logic for detecting whether -rdynamic\nis necessary and supported uses an appropriate objdump for $host\nbinaries (running on $build) in cases where $host is $build or\n$target.\n\nHowever, it is missing such logic in the case where $host is neither\n$build nor $target, resulting in the compilers not being linked with\n-rdynamic and plugins not being usable with such a compiler.  In fact\n$ac_cv_prog_OBJDUMP, as used when $build \u003d $host, is always an objdump\nfor $host binaries that runs on $build; that is, it\u0027s appropriate to\nuse in this case as well.\n\nTested in such a configuration that it does result in cc1 being linked\nwith -rdynamic as expected.  Also bootstrapped with no regressions for\nx86_64-pc-linux-gnu.\n\nconfig/\n\t* gcc-plugin.m4 (GCC_ENABLE_PLUGINS): Use\n\texport_sym_check\u003d\"$ac_cv_prog_OBJDUMP -T\" also when host is not\n\tbuild or target.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c731a6fab3831e3c089c51bf1ada558b8befd5ca",
      "old_mode": 33188,
      "old_path": "config/gcc-plugin.m4",
      "new_id": "c30cfdd8fadba3fb54f89d6afe8edb3441206dba",
      "new_mode": 33188,
      "new_path": "config/gcc-plugin.m4"
    }
  ]
}