This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Separate preprocess and compile: hack or feature?

From: Nathan Sidwell <nathan at acm dot org>
To: Boris Kolpackov <boris at codesynthesis dot com>, gcc at gcc dot gnu dot org
Date: Thu, 11 May 2017 09:48:36 -0400
Subject: Re: Separate preprocess and compile: hack or feature?
Authentication-results: sourceware.org; auth=none
References: <boris.20170511111208@codesynthesis.com>

Hi Boris

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[1] for other reasons.

How c++ modules fit into a build system is currently an open question.Richard Smith & I have talked about it, but with no firm conclusion.However, I think that breaking out the preprocessor is not the rightanswer. We were leaning more to some kind of hook in the compiler toanswer 'I can't find module FOO, where is it?'


nathan

--
Nathan Sidwell

Follow-Ups:
- Re: Separate preprocess and compile: hack or feature?
  - From: Boris Kolpackov

References:
- Separate preprocess and compile: hack or feature?
  - From: Boris Kolpackov

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]