In the past, the libgo version number has always matched the Go version,
not the gcc release.
The libgo for Go 1.7 and Go 1.8 are not the same. If someone wanted to
build gccgo for Go 1.7 using an old commit
maybe for testing or comparison purposes, the libgo version would not
identify which one it was because
libgo.so.10 could be either Go 1.7 or 1.8. Maybe nobody cares about
doing that. It's not a huge deal to me but
it would be a point of confusion.
GCC 6.x was Go 1.6.
On 01/17/2017 10:09 AM, Jakub Jelinek wrote:
On Tue, Jan 17, 2017 at 10:03:25AM -0600, Lynn A. Boger wrote:
I think this is missing the update of the libgo version number.
Why? GCC 6.x shipped with libgo.so.9, so I don't see anything wrong
on 7.x shipping libgo.so.10.
Jakub
