From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamie Lokier To: law@cygnus.com, "H.J. Lu" Cc: egcs@egcs.cygnus.com, GNU C Library Subject: Re: __register_frame_info & shared library compatibility Date: Fri, 30 Apr 1999 23:15:00 -0000 Message-ID: <19990408222418.C21807@pcep-jamie.cern.ch> References: <29339.923601663@upchuck> X-SW-Source: 1999-04n/msg00282.html Message-ID: <19990430231500.T9A0Wmtr3swybH9brQT20jCIJDLKO2kgs4ZdlGibTjQ@z> [BTW Jeffrey, your from: address is bouncing] > No, this is an egcs problem. We can't have these kinds of problems show > up when folks rebuild their libraries with newer versions of the compiler. > > Can I be any clearer? The policy is pretty clear. The danger is that we get locked in to including bloat in all binaries, that can't ever be removed. I'm interested in a solution to that long term problem. If we have to include the bloat in the interim to provide binary compatibility, that is fine. Though frankly, the bloat due to the redundant .eh_frame in C binaries much more significant. Is throwing an exception through C really supposed to have defined behaviour? -- Jamie