public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libgcc/58120] New: libgcc.a and libgcc_eh.a have incorrect symbol visibility
@ 2013-08-10 16:14 jeremyhu at macports dot org
  0 siblings, 0 replies; only message in thread
From: jeremyhu at macports dot org @ 2013-08-10 16:14 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58120

            Bug ID: 58120
           Summary: libgcc.a and libgcc_eh.a have incorrect symbol
                    visibility
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgcc
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jeremyhu at macports dot org

If one builds a dylib using static libgcc.a, the libgcc symbols will be
exported by that library.  One can mitigate this using an
-unexported_symbols_list, but that is sub-optimal.  The static archives should
have the expected visibility to prevent re-export when built into a dylib.

This is an issue on OS X, and I assume the same issue exists on other platforms
as well.


^ permalink raw reply	[flat|nested] only message in thread
only message in thread, other threads:[~2013-08-10 16:14 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-08-10 16:14 [Bug libgcc/58120] New: libgcc.a and libgcc_eh.a have incorrect symbol visibility jeremyhu at macports dot org

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).