This is the mail archive of the
mailing list for the GCC project.
Separate preprocess and compile: hack or feature?
- From: Boris Kolpackov <boris at codesynthesis dot com>
- To: gcc at gcc dot gnu dot org
- Date: Thu, 11 May 2017 11:13:35 +0200
- Subject: Separate preprocess and compile: hack or feature?
- Authentication-results: sourceware.org; auth=none
In the build system I am working on we are looking at always performing
the preprocessing and then C/C++ compilation as two separate gcc/g++
invocations. The main reason is support for distributed compilation but
see here for other reasons.
I realize that tools like ccache/distcc have been relying on this for
a while (though see the 'direct' mode in ccache and 'pump' in distcc).
However, some compilers apparently do not support this (for example,
VC; see the above link for details).
So I wonder, in the context of GCC, if this is just a hack that happens
to work "for now" or if this is a feature that is expected to continue
Also, has anyone seen/heard of any real-world issues with compiling
preprocessed source code?