)]}'
{
  "commit": "e911f90a4035ee6a70d9b608ef35c6870aa86fdb",
  "tree": "5af9744f81c83f7fdb69bb6b2aa182c6a41fabc6",
  "parents": [
    "a2d129b792cc49224f98c83d2279b2e19bfa700f"
  ],
  "author": {
    "name": "Kevin Gleason",
    "email": "gleasonk@google.com",
    "time": "Fri Apr 11 13:00:47 2025 -0500"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Apr 11 13:00:47 2025 -0500"
  },
  "message": "[mlir] Add support for broader range of input files in generate-test-checks.py (#134327)\n\nA few additions:\n\n- Lines with `{{`: These can show up if serializing non-MLIR info into\nstring attrs `my.attr \u003d {{proto}, {...}}`. String escape the opening\n`{{`, given that check lines are generated this has no effect on\n`{{.*}}` etc in generated lines.\n- File split line: Normally these are skipped because of their indent\nlevel, but if using `--starts_from_scope\u003d0` to generate checks for the\n`module {...} {` line, and since MLIR opt tools emit file split lines by\ndefault, some `CHECK: // -----` lines were emit.\n- (edit removed this, fixed by\nhttps://github.com/llvm/llvm-project/pull/134364) AttrAliases: I\u0027m not\nsure if I\u0027m missing something for the attribute parser to work\ncorrectly, but I was getting many `#[[?]]` for all dialect attrs. Only\nuse the attr aliasing if there\u0027s a match.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "07440990a58d70552cef00b31a504efc5c25dbf4",
      "old_mode": 33261,
      "old_path": "mlir/utils/generate-test-checks.py",
      "new_id": "394ef7e0f7da05f363c0f5c12e71d686459ead14",
      "new_mode": 33261,
      "new_path": "mlir/utils/generate-test-checks.py"
    }
  ]
}