From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7154 invoked by alias); 8 May 2013 23:41:03 -0000 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 Received: (qmail 7092 invoked by uid 48); 8 May 2013 23:40:52 -0000 From: "Bernhard.Rosenkranzer at linaro dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/57221] New: [4.8/4.9 regression] libgcc symbol visibility changes break Android blobs Date: Wed, 08 May 2013 23:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libgcc X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: Bernhard.Rosenkranzer at linaro dot org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 X-SW-Source: 2013-05/txt/msg00575.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57221 Bug #: 57221 Summary: [4.8/4.9 regression] libgcc symbol visibility changes break Android blobs Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgcc AssignedTo: unassigned@gcc.gnu.org ReportedBy: Bernhard.Rosenkranzer@linaro.org Created attachment 30064 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30064 Proposed fix The changes in libgcc symbol visibilities that got into 4.8 (http://gcc.gnu.org/ml/gcc-patches/2012-08/msg01462.html) break important Android blobs. Bionic (Android's libc) has some rather weird hacks that expose libgcc.a's __aeabi_uidiv and friends to applications linking to Bionic. The changed symbol visibility breaks this, resulting in e.g. a Galaxy Nexus Android build done with gcc 4.8 failing to boot to UI because it can't load its graphics drivers. It may make sense to change symbol visibility back to default if the target is Android. I've attached a patch that does that.