Am 19.06.2013 01:50, schrieb Ian Lance Taylor: > This patch to gccgo changes the representation of values of function > type. They used to be a pointer to function code, like a C function > pointer. They are now a pointer to a struct. The first field of the > struct points to the function code. The remaining fields, if any, are > the addresses of variables referenced in enclosing functions. For each > call to a function, the address of the function descriptor is passed as > the last argument. > > This lets us avoid generating trampolines, and removes the use > of writable/executable sections of the heap. > > This is also a prerequisite to a new Go 1.1 feature, method values. > > Bootstrapped and ran Go testsuite on x86_64-unknown-linux-gnu. > Committed to mainline and 4.8 branch.
so this did change the soname for libgo to 5 on the trunk, and to 4 on the branch. We had this discussion before, and then decided to revert this kind of change on the 4.7 branch. This time the release notes had a hint that the Go support would be updated to v1.1 in a bug fix release, so maybe it is ok. Will this the only soname bump on the way to Go 1.1 support, or are there more changes/version bumps planned on this way? Matthias
