public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Bernhard.Rosenkranzer at linaro dot org" <gcc-bugzilla@gcc.gnu.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 [thread overview]
Message-ID: <bug-57221-4@http.gcc.gnu.org/bugzilla/> (raw)
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.
next reply other threads:[~2013-05-08 23:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 23:41 Bernhard.Rosenkranzer at linaro dot org [this message]
2013-05-08 23:52 ` [Bug libgcc/57221] " pinskia at gcc dot gnu.org
2013-05-09 0:09 ` Bernhard.Rosenkranzer at linaro dot org
2013-05-09 0:51 ` Bernhard.Rosenkranzer at linaro dot org
2013-05-15 13:29 ` rguenth at gcc dot gnu.org
2013-05-31 11:00 ` jakub at gcc dot gnu.org
2013-10-16 9:51 ` jakub at gcc dot gnu.org
2013-10-30 12:20 ` rguenth at gcc dot gnu.org
2014-05-22 9:07 ` [Bug libgcc/57221] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:38 ` [Bug libgcc/57221] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-03-13 12:11 ` ramana at gcc dot gnu.org
2015-03-23 13:39 ` mkuvyrkov at gcc dot gnu.org
2015-06-23 8:21 ` [Bug libgcc/57221] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 20:10 ` [Bug libgcc/57221] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:36 ` jakub at gcc dot gnu.org
2021-05-04 12:31 ` [Bug libgcc/57221] [8/9/10/11/12 " rguenth at gcc dot gnu.org
2021-05-14 9:46 ` [Bug libgcc/57221] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01 8:05 ` rguenth at gcc dot gnu.org
2022-05-27 9:34 ` [Bug libgcc/57221] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:30 ` jakub at gcc dot gnu.org
2023-07-07 10:29 ` [Bug libgcc/57221] [11/12/13/14 " rguenth at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-57221-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).