This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug go/54918] libgo.so.0 is not runtime compatible between gcc-4.6.2 and gcc-4.7.x
- From: "gafton at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 15 Oct 2012 17:53:46 +0000
- Subject: [Bug go/54918] libgo.so.0 is not runtime compatible between gcc-4.6.2 and gcc-4.7.x
- Auto-submitted: auto-generated
- References: <bug-54918-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54918
--- Comment #2 from Cristian Gafton <gafton at gmail dot com> 2012-10-15 17:53:46 UTC ---
(In reply to comment #1)
> incompatible as in missing symbols or in incompatible behavior between
> different
> symbols?
I have only run across missing symbols, but it looks like none of the changes
in the libgo library have been dressed with any sort of symbol versioning, so
there could also be some incompatible behaviour changes. I have not studied the
libgo source enough to make that determination though; the missing symbols
make it hard to test older binaries to check for behavioral changes.