public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/20617] [4.0/4.1 regression] shared SH libgcc is exporting too many symbols
Date: Wed, 06 Apr 2005 19:32:00 -0000	[thread overview]
Message-ID: <20050406193211.17417.qmail@sourceware.org> (raw)
In-Reply-To: <20050324112142.20617.amylaar@gcc.gnu.org>


------- Additional Comments From amylaar at gcc dot gnu dot org  2005-04-06 19:32 -------
(In reply to comment #17)
> Subject: Re:  [4.0/4.1 regression] shared SH libgcc is
>  exporting too many symbols
> 
> "joern dot rennecke at st dot com" <gcc-bugzilla@gcc.gnu.org> writes:
> 
> [LIB1FUNCS_ST]
> > Won't this have the effect that any of the referenced symbols remain
> > undefined in libgc_s.so, and will get a GOT (and in 4.0 even a PLT
> > entry) in libgcc.so? 
> 
> You can avoid this problem by including libgcc.a in the final link of
> libgcc_s.so.  Every global symbol in libgcc.a is or ought to be hidden
> (that being a goal of all the work I put in on libgcc construction
> last year) so the effect will be that libgcc_s.so gets private copies
> of everything that it actually uses, but nothing more.
> 
I just had a look, and actually there appears to be no variable called
LIB1FUNCS_ST.  There is one called LIB2FUNCS_ST, but that's a place for
machine-independent static libgcc2 parts, and one called
LIB2FUNCS_STATIC_EXTRA.  The latter is actually a list of filenames, no
a list of pieces inside lib1funcs.asm, so I couldn't use it without major
butchery of the SH assembler support functions.

-- 


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


  parent reply	other threads:[~2005-04-06 19:32 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24 11:22 [Bug target/20617] New: " amylaar at gcc dot gnu dot org
2005-03-24 11:43 ` [Bug target/20617] " amylaar at gcc dot gnu dot org
2005-03-24 12:12 ` amylaar at gcc dot gnu dot org
2005-03-24 14:47 ` pinskia at gcc dot gnu dot org
2005-03-24 16:06 ` zack at codesourcery dot com
2005-03-24 16:25 ` cvs-commit at gcc dot gnu dot org
2005-03-24 16:31 ` joern dot rennecke at st dot com
2005-03-24 16:49 ` drow at gcc dot gnu dot org
2005-03-24 17:01 ` [Bug target/20617] [4.0/4.1 regression] " mmitchel at gcc dot gnu dot org
2005-03-24 17:06 ` mmitchel at gcc dot gnu dot org
2005-03-24 17:31 ` schwab at suse dot de
2005-03-24 18:06 ` joern dot rennecke at st dot com
2005-03-24 18:17 ` joern dot rennecke at st dot com
2005-03-24 18:46 ` zack at codesourcery dot com
2005-03-24 19:36 ` mrs at apple dot com
2005-03-24 21:08 ` joern dot rennecke at st dot com
2005-03-24 21:25 ` joern dot rennecke at st dot com
2005-03-24 22:48 ` kkojima at gcc dot gnu dot org
2005-03-24 22:53 ` geoffk at gcc dot gnu dot org
2005-03-24 22:54 ` zack at codesourcery dot com
2005-03-24 23:49 ` joern dot rennecke at st dot com
2005-03-24 23:54 ` zack at codesourcery dot com
2005-03-25  0:30 ` kkojima at gcc dot gnu dot org
2005-03-29 11:54 ` joern dot rennecke at st dot com
2005-03-29 12:43 ` kkojima at gcc dot gnu dot org
2005-04-06 19:32 ` amylaar at gcc dot gnu dot org [this message]
2005-04-06 20:03 ` zack at codesourcery dot com
2005-07-06 14:28 ` pinskia at gcc dot gnu dot org
2005-07-16  3:46 ` zack at codesourcery dot com
2005-07-16 20:14 ` pinskia at gcc dot gnu dot org
2005-09-27 16:14 ` [Bug target/20617] [4.0/4.1 Regression] " mmitchel at gcc dot gnu dot org
     [not found] <bug-20617-5394@http.gcc.gnu.org/bugzilla/>
2005-10-13 19:57 ` pinskia at gcc dot gnu dot org
2005-10-30 23:38 ` pinskia at gcc dot gnu dot 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=20050406193211.17417.qmail@sourceware.org \
    --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).