payload: {"push_id":4087174009,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"f840368602ba6e9cf46b9572bc8000a6c88a041d","before":"a8864f4a61ac4d57083131e6001e3a2ce5a11632","commits":[{"sha":"1eedf33ccdc5170c9cd8151903cd7025646a5c55","author":{"name":"gccadmin","email":"2aa286f04500e4a7a9254cbd74d9060dce58402c@138bc75d-0d04-0410-961f-82ee72b054a4"},"message":"Daily bump.\n\ngit-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@276227 138bc75d-0d04-0410-961f-82ee72b054a4","distinct":true,"url":"https://api.github.com/repos/kraj/gcc/commits/1eedf33ccdc5170c9cd8151903cd7025646a5c55"},{"sha":"f840368602ba6e9cf46b9572bc8000a6c88a041d","author":{"name":"ian","email":"57a33a5496950fec8433e4dd83347673459dcdfc@138bc75d-0d04-0410-961f-82ee72b054a4"},"message":"    compiler: resolve importing ambiguity for more complex function calls\n    \n    Tweak the exporter for inlinable function bodies to work around a\n    problem with importing of function calls whose function expressions\n    are not simple function names. In the bug in question, the function\n    body exporter was writing out a function call of the form\n    \n           (*(*FuncTyp)(var))(arg)\n    \n    which produced an export data representation of\n    \n           *$convert(<type 5>, var)(x)\n    \n    which is hard to parse unambiguously. Fix: change the export data\n    emitter to introduce parens around the function expression for more\n    complex calls.\n    \n    Testcase for this bug is in CL 197217.\n    \n    Fixes golang/go#34503.\n    \n    Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/197122\n\n\ngit-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@276228 138bc75d-0d04-0410-961f-82ee72b054a4","distinct":true,"url":"https://api.github.com/repos/kraj/gcc/commits/f840368602ba6e9cf46b9572bc8000a6c88a041d"}]}
other: {"actor":{"display_login":"kraj"}}