This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libgcc problems with shared libraries
- To: egcs at cygnus dot com
- Subject: Re: libgcc problems with shared libraries
- From: David Edelsohn <dje at watson dot ibm dot com>
- Date: Wed, 14 Jan 1998 13:45:41 -0500
- Cc: law at cygnus dot com
>>>>> Andrey Slepuhin writes:
Andrey> Some problems with incorrect executables were solved by adding
Andrey> "cror 31,31,31" after each "bl ._savef14" instruction in *.s
Andrey> files and recompiling them. So, this is definitely egcs bug
Andrey> (I'm using 971225 snapshot). May be there are other similar bugs -
Andrey> I don't know (at least not all executables became correct).
Andrey> What I really don't understand - how this is referred to my
Andrey> experiments with libgcc, i.e. why absence of cror instructions
Andrey> didn't break execution earlier?
These save and restore calls should be local to the program. The
only way they could be failing is if the linker is using a different copy
of those routines. There are a number of symbols that should never be
re-exported from a library. _savef[0-9][0-9]$ and _restf[0-9][0-9]$ are
two such regexs examples. This is another example of the braindamage automatic
exporting others have added to collect2 coming back to cause problems.
David