Cutting over to cpplib as default preprocessor

Cutting over to cpplib as default preprocessor

[Zack Weinberg]

We have been planning to switch to cpplib as the default preprocessor
for more than a year now.  All of the critical bugs that I am aware of
have been fixed, there's no performance loss and no regressions in the
test suite, it can handle glibc and X11.

Now there's a fairly messy situation with C++ comments (see
http://gcc.gnu.org/ml/gcc-bugs/2000-01/msg00637.html and the thread it
spawned) which I do not believe is practical to fix in cccp.  There is
a minor issue of standards conformance involved, too - failure to
issue a mandatory diagnostic even in -pedantic mode.

Rather than continue to hack up cccp, I would like to switch on
--enable-cpplib by default in the EGCS tree.  I am not going to go all
the way to --enable-c-cpplib yet because there are still some critical
issues with the integrated preprocessor (e.g. -save-temps won't give
you an .i file if you do that).

If there are no objections I will make the switch on Friday morning.

zw

Re: Cutting over to cpplib as default preprocessor

[Richard Henderson]

On Wed, Jan 26, 2000 at 02:27:06PM -0800, Zack Weinberg wrote:
> Rather than continue to hack up cccp, I would like to switch on
> --enable-cpplib by default in the EGCS tree.

No objections here.


r~

Re: Cutting over to cpplib as default preprocessor

[Jeffrey A Law]

  In message < 20000127021038.C4557@cygnus.com >you write:
  > On Wed, Jan 26, 2000 at 02:27:06PM -0800, Zack Weinberg wrote:
  > > Rather than continue to hack up cccp, I would like to switch on
  > > --enable-cpplib by default in the EGCS tree.
  > 
  > No objections here.
Similarly.  It's time to start shaking out the final bugs in cpplib and
prepare to transition the old cpp out of the source tree.

jeff