)]}'
{
  "commit": "ada763b9eeb07eaaa05a2cc58163bd7088ebb165",
  "tree": "88a569b65e934f10a784c56432e058d64ea3b785",
  "parents": [
    "c137c0a87b58da4c5a8af7d18681ec60361c156c"
  ],
  "author": {
    "name": "Jason Rhinelander",
    "email": "jason@imaginary.ca",
    "time": "Thu Feb 09 21:53:38 2017 -0500"
  },
  "committer": {
    "name": "Wenzel Jakob",
    "email": "wenzel.jakob@epfl.ch",
    "time": "Tue Feb 14 10:59:59 2017 +0100"
  },
  "message": "Temporary gcc travis-ci build fixes\n\nRecent gcc snapshots (both gcc 7 snapshots and recent gcc 6 stable\nbranch snapshots) are triggering an upstream gcc bug when -flto is\nenabled (https://gcc.gnu.org/bugzilla/show_bug.cgi?id\u003d79296).  This has\nbeen hitting the gcc-7 builds for a while now, but is going to start\nhitting the debian testing builds in a few days as well.\n\nThe issue is triggered by using -flto in combination with structs or\nclasses declared in a function, as done in test_alias_initialization,\ntest_isses, test_methods_and_attributes (and possibly more).\n\nI\u0027m subscribed to the upstream bug, and will submit another PR to\nreenable LTO once a fixed gcc is available.\n\nThe gcc-7 build also generates some warnings; just ignore them for now\n(by turning off -Werror).\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c19cab3ddb927d711750e21d8cb5c5ad936e11fe",
      "old_mode": 33188,
      "old_path": ".travis.yml",
      "new_id": "d510047cc975b481720d052ea12ffaba6ab2e8d0",
      "new_mode": 33188,
      "new_path": ".travis.yml"
    }
  ]
}