gcc 2.8.0 is broken on linux/x86 and more bug

[H.J. Lu]

>   > I think that is what my patch does. It keeps the old name and
>   > appends _new to new interface. It seems to work for me.
> I don't believe it handles the "free" issue correctly, then again, I'm
> not real familiar with that code.
> 
> Please explain to me how it works if both register_frame and
> register_frame_new are are called by one program.  
> 

How does register_frame/register_frame_new get called? They are
called by crtbegin.o/collect2. User doesn't use them directly.
Since they are under our control, we always call the right one.

My glibc.so calls register_frame. But the binaries generated by
new egcs and gcc 2.8.0 call register_frame_new. In my environment
register_frame/register_frame_new are mixed when libc.so is used.


-- 
H.J. Lu (hjl@gnu.org)