[distcc] gcc bootstraps with distcc

[Alexandre Oliva]

On Aug  4, 2003, Neil Booth <neil@daikokuya.co.uk> wrote:

> So it seems that it moves the expansion of a macro down to its last
> line.  Is that the effect?

Yup.  Just the same effect that we get with the integrated
preprocessor.

> Why is this

>       || (parsing_args && pfile->context && pfile->context->prev))

> necessary?

I wasn't sure it was necessary.  I only tried to limit the effects of
my change.  I don't see how it would be possible for us to take a line
change while processing a macro.

> Right, so a Fortran user now can get line breaks that he couldn't
> before

Only if they have line breaks in their macro invocations.

> Am I right that escaped newlines and multi-line comments still
> cause problems for what you're trying to do?

I don't have any remaining problems in bootstrapping GCC with a mix of
separate and integrate preprocessing after this patch.  Debugging
information is now identical regardless of which preprocessing
mechanism is used, but I don't know how much coverage a GCC bootstrap
represents in this regard.  I know I had lots of differences before
the patch, but I haven't examined the complete set of sources of
differences.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer