This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Export bits of the demangler's internal interface


On Mon, Jan 05, 2004 at 01:20:23PM -0500, DJ Delorie wrote:
> 
> > What do you (and DJ, and anybody else) think about this sort of
> > interface?
> 
> That is acceptable.
> 
> > I considered hiding struct demangle_component and providing accessor
> > functions, but I decided that that wasn't worth it.  I don't think we
> > need to worry about binary compatibility among different releases.
> 
> We do, there is at least one OS that ships a shared libiberty.so.

Which?  Merely curious.

> However, I think a suitably obvious comment in cp-demangle.h (or
> wherever) explaining that we do NOT provide binary compatibility to
> these functions should take care of that.  Unfortunately, that means
> that gdb won't be able to link with a shared libiberty on that (or
> those) platforms.  Personally, I'm not worried about it, since they
> would simply need to bump libiberty if they bumped gdb, or when the
> user builds their own gdb they won't get a shared libiberty anyway.

Yeah.  They would have to patch the gdb build to make it use a shared
libiberty anyway, since it hardcodes ../libiberty/libiberty.a.  I can't
really see the benefit of using a shared one... it's so small...

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]