)]}'
{
  "commit": "3968d5fb552fbd2e0687a20e8221e4e08d49da04",
  "tree": "2bfeda470be7cde173abde9b2d9d4b54f4042198",
  "parents": [
    "a880082f559dcc0d8c3bfd6c60e38cb3151eb0d9"
  ],
  "author": {
    "name": "Harald Anlauf",
    "email": "anlauf@gmx.de",
    "time": "Thu May 28 22:49:26 2026 +0200"
  },
  "committer": {
    "name": "Harald Anlauf",
    "email": "anlauf@gmx.de",
    "time": "Mon Jun 01 21:19:26 2026 +0200"
  },
  "message": "Fortran: checking of passed character length [PR125393]\n\nCommit r16-3462 enhanced checking of character length passed to a character\ndummy.  However, when the actual argument was an array element, its storage\nsize was estimated from all elements up to the end of the array.  This\ncould give a bogus warning when the dummy argument was of a scalar\ncharacter type.  Fix check for this case to actually compare the character\nlengths of actual and dummy.\n\n\tPR fortran/125393\n\ngcc/fortran/ChangeLog:\n\n\t* interface.cc (get_expr_storage_size): Additionally return\n\tcharacter length.\n\t(gfc_compare_actual_formal): When the formal is a scalar character\n\tvariable, use character lengths, not array storage size for check.\n\ngcc/testsuite/ChangeLog:\n\n\t* gfortran.dg/argument_checking_28.f90: New test.\n\n(cherry picked from commit 47bb24546297ef6812d69bc800ec005fc7e567e9)\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d25cf0591b7f1ec7f2885559884d5be8f0a1de72",
      "old_mode": 33188,
      "old_path": "gcc/fortran/interface.cc",
      "new_id": "3181ca9c11b99b3e5a8fd38a8aa1b8f0d4b87dbe",
      "new_mode": 33188,
      "new_path": "gcc/fortran/interface.cc"
    },
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "fb9ec4d70eaec6e2bcb61473ec2e73f887db6019",
      "new_mode": 33188,
      "new_path": "gcc/testsuite/gfortran.dg/argument_checking_28.f90"
    }
  ]
}
