From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31405 invoked by alias); 15 Oct 2012 17:54:03 -0000 Received: (qmail 31363 invoked by uid 48); 15 Oct 2012 17:53:47 -0000 From: "gafton at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug go/54918] libgo.so.0 is not runtime compatible between gcc-4.6.2 and gcc-4.7.x Date: Mon, 15 Oct 2012 17:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: go X-Bugzilla-Keywords: ABI X-Bugzilla-Severity: major X-Bugzilla-Who: gafton at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ian at airs dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-10/txt/msg01422.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54918 --- Comment #2 from Cristian Gafton 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.