GCC 3.0 Release Criteria

[Chip Salzenberg]

According to Geoff Keating:
> Actually, this doesn't happen for __register_frame_info under linux:
> 
> 00000000  w   DF *UND*  000000e4  GLIBC_2.1.3 __cxa_finalize
> 00000000  w   DF *UND*  000000f0  GLIBC_2.0   __deregister_frame_info
> 00000000  w   DF *UND*  000000a8  GLIBC_2.0   __register_frame_info
> 
> I don't understand why, it's something to do with their being exported
> from libc.so.

I asked Ulrich about that, and he said that they're still being
exported from glibc2 because in glibc1 they were exporting them,
and if they stopped exporting them they'd break bincompat.
-- 
Chip Salzenberg              - a.k.a. -              <chip@valinux.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
    but he stepped in a wormhole and had to go in early."  // MST3K