------- Additional Comments From joern dot rennecke at st dot com 2005-03-24 21:25 ------- Subject: Re: [4.0/4.1 regression] shared SH libgcc is exporting too many symbols
zack at codesourcery dot com wrote: > You may want to consider use of LIB1FUNCS_ST instead of LIB1FUNCS, so >that the symbols are not put into libgcc_s.so in the first place. > 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? Some functions may not ue the PLT because of register usage. And most of the rest is really smaller than a PLT entry, so a copy should be linked hidden into every dso that needs it. Including libgcc.so . >Note that the private copy that you had, did *not* exclude hundreds of >lib1funcs.asm symbols. The only symbols not in it, that were in >libgcc-std.ver, and were not due to people forgetting to update it, >are the symbols currently listed in sh/libgcc-excl.ver. > I didn't say hundreds - I said some hundred. greps counts 94 hidden functions ans aliases in my current lib1funcs.asm working copy. The largest group, with 40 members, is probably the set of movstr* and movmem* functions, none of which was mentioned in libgcc-std.ver (and hence was excluded), and none of which is mentioned in sh/libgcc-excl.ver (and hence is now included). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20617
