Re: Horrible compiletimes and memory usage while compiling a parser with X3

On 06/11/2016 6:03 AM, Exagon wrote:
> I dont believe I can break this down to one cpp.

Why not? I was able to cut and copy the files into one cpp file
and build. See my other post.

> I can set up a github repo.
> This is not only a problem with gcc I tried gcc and clang and both are using
> up to 32GB Ram and the resulting binarys are up to 1.6 Gb big with both gcc
> and clang.

Odd. I am not seeing the problem. Your code and the one posted by Seth
builds fine in a few seconds on my machine.

> But again I dont think I can break this down to a simple mcve.
> Please tell me if you are interested in me setting up a repo with the
> problem at github, if so I will do it tomorrow.

Ok, if you can provide a bjam file, that would work.

Regards,
-- 
Joel de Guzman
http://www.ciere.com
http://boost-spirit.com
http://www.cycfi.com/

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi