Re: sharing libcpp between GDB and GCC

Zack Weinberg
2002-03-26T04:07:39Z

On Mon, Mar 25, 2002 at 06:40:47PM -0500, Jim Blandy wrote:
>
> I assume there's general agreement that, if GDB and GCC are going to
> share libcpp, we'll want to pull libcpp out into its own top-level
> directory, with its own makefile and configure script, and move its
> header files into the top-level #include directory. Is that so?

Yes.

> - The GCC folks could do this extraction, ensuring that GCC continues
> to work. Then we can copy that directory over into GDB's
> repository, and begin the libcpp/GDB integration.

I like this plan, and am provisionally willing to do the work, with
the warning that we're coming up on the "no more major structural
changes" freeze deadline for GCC 3.2 and there are several other major
structural changes I want to squeeze in (new numeric-constant parser,
tm.h out of config.h, continued floating point overhaul).[1] And I'll be
out of touch, and not hacking on anything, from Wednesday through the
beginning of next week.

It should not be terribly hard to do though. There's two hurdles.
First, we have to dissociate cpplib from GCC's target configuration
entirely; thanks to Eric's integrated-preprocessor patch, it's now
practical to shift most of that to the C front end proper. Second,
the symbol table has to be split up between the two directories while
somehow maintaining its integration in the final binary. There's also
a bunch of shared code, but the gcc subdir can just reference object
files from the libcpp subdir.

It will be another reason for bootstrap to happen at the top level; I
would rather not do that myself.

zw

[1] If people feel that all or some of these can happen during the
"smaller improvements only" phase, I'll deprioritize them a bit.