Hi,
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.
I realize that tools like ccache/distcc have been
On 11 May 2017 at 10:13, Boris Kolpackov wrote:
> Hi,
>
> 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
On 10 May 2017 at 23:14, Daniel Santos wrote:
> Well my primary goal is programming with values that are constant in the
> compiler. There is no language in any C specification (that I'm aware of)
> for a "compile-time constant", but the concept is very important. So just
> because some expressio
I see from https://gcc.gnu.org/install/test.html that it's possible to run
tests in parallel. I get the impression from gcc/Makefile that the check
concerned has to be set up in the Makefile (in my build tree, configured with
--target=x86_64-apple-darwin16
--enable-languages=c,c++,ada,fortran,o
On Thu, May 11, 2017 at 11:06:13AM +0100, Jonathan Wakely wrote:
> It's absolutely a supported feature. Why else do you think the manual
> would discuss so many options for preprocessing, and options for
> compiling preprocessed code?
> https://gcc.gnu.org/onlinedocs/gcc/Overall-Options.html seems
On Thu, May 11, 2017 at 11:12:24AM +0100, Jonathan Wakely wrote:
> On 10 May 2017 at 23:14, Daniel Santos wrote:
> > Well my primary goal is programming with values that are constant in the
> > compiler. There is no language in any C specification (that I'm aware of)
> > for a "compile-time consta
On 11/05/17 11:43, Simon Wright wrote:
I see from https://gcc.gnu.org/install/test.html that it's possible to run
tests in parallel. I get the impression from gcc/Makefile that the check
concerned has to be set up in the Makefile (in my build tree, configured with
--target=x86_64-apple-darwin
On Thu, May 11, 2017 at 11:50:21AM +0100, Kyrill Tkachov wrote:
>
> On 11/05/17 11:43, Simon Wright wrote:
> > I see from https://gcc.gnu.org/install/test.html that it's possible to run
> > tests in parallel. I get the impression from gcc/Makefile that the check
> > concerned has to be set up in
On Thu, May 11, 2017 at 12:43 PM, Jakub Jelinek wrote:
> On Thu, May 11, 2017 at 11:06:13AM +0100, Jonathan Wakely wrote:
>> It's absolutely a supported feature. Why else do you think the manual
>> would discuss so many options for preprocessing, and options for
>> compiling preprocessed code?
>>
Hi Jakub,
Jakub Jelinek writes:
> Especially in recent GCC versions the amount of differences for warnings and
> errors keeps dramatically increasing, with separate preprocessing simply
> too much information is lost (macro contexts, lint style comments, exact
> locations, system header issues,
On 11 May 2017, at 11:50, Kyrill Tkachov wrote:
> On 11/05/17 11:43, Simon Wright wrote:
>> I see from https://gcc.gnu.org/install/test.html that it's possible to run
>> tests in parallel. I get the impression from gcc/Makefile that the check
>> concerned has to be set up in the Makefile (in my
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
On Thu, 11 May 2017, Jonathan Wakely wrote:
> On 10 May 2017 at 23:14, Daniel Santos wrote:
> > Well my primary goal is programming with values that are constant in the
> > compiler. There is no language in any C specification (that I'm aware of)
> > for a "compile-time constant", but the concept
Hi Nathan,
Nathan Sidwell writes:
> 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 right
> answer.
Handling modules is one of the least
Snapshot gcc-7-20170511 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20170511/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7
15 matches
Mail list logo