This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: __register_frame_info problem on Alpha
- To: drepper at cygnus dot com (Ulrich Drepper)
- Subject: Re: __register_frame_info problem on Alpha
- From: Jeffrey A Law <law at upchuck dot cygnus dot com>
- Date: Wed, 26 May 1999 12:00:43 -0600
- cc: Thorsten Kukuk <kukuk at suse dot de>, "H.J. Lu" <hjl at lucon dot org>, egcs at egcs dot cygnus dot com, libc-hacker at sourceware dot cygnus dot com
- Reply-To: law at cygnus dot com
In message <r2pv3n3eui.fsf@happy.cygnus.com>you write:
> Thorsten Kukuk <kukuk@suse.de> writes:
>
> > I would like to not see this symbol in libc.so.6.1. Or we will have
> > again this problems, because current Alpha distributions doesn't have
> > this symbol, and our SuSE Linux AXP Beta also. So the first
> > distribution after a new egcs/gcc version will have this symbols,
> > and we have the problems again.
>
> We cannot have this function simply missing. It is actively used.
> And since libgcc is no shared object it is picked up and put in the
> shared lib.
>
> If the compiler has such a big change there is no backward
> compatibility guaranteed. Simply let the people use the right
> versions. If somebody updates a compiler independent from the rest of
> the distribution s/he must be prepared to do some more work (e.g.,
> installing a new libc which you can provide).
No. That's not our approach to binary compatibility. We have to do better.
People should be able to upgrade their compiler independently of the rest
of their system. They should be able to rebuild libraries with that new
compiler and applications which use those libraries should still work.
We have to take binary compatibility much more seriously than we have in
the past. Simply ignoring it and saying "you have to upgrade the entire
distribution" is not acceptable.
jeff