This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Merge cpplib and front end hashtables, part 1
On Wed, May 16, 2001 at 01:41:48PM -0700, Stan Shebs wrote:
> (Just the mechanics of using cpplib in GDB will be interesting - we
> will probably need cpplib to be a sibling of libiberty for
> instance).
Yes, we're going to want to do that eventually. The only things
keeping cpplib in the gcc subdirectory right now are the information
in cppdefault.c and the knowledge of where to install cpp0. I would
like to see everything in cppdefault.c be moved into the driver and
communicated to cpp0/cc1 with command line switches. This will also
permit us to shift a lot of ugly command line option handling into the
driver (-iprefix etc). Some of the automatic #defines probably belong
in the driver, too.
The knowledge of where to install cpp0 ($(libsubdir), that is) can be
shifted to the top-level configure; that's a simple matter of programming.
There are infrastructural changes that should happen at the same
time. For instance, the bootstrap logic should move to top level and
operate on multiple directories - at least libiberty, libcpp, gcc;
arguably as and ld, if present, should get 3-staged as well...
--
zw This is, no doubt, the rational strategy; quite possibly the
only one that will work. But it ignores the exigiencies of
the tenure system and is therefore impractical.
-- Jerry Fodor, _The Mind Doesn't Work That Way_