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

On 26/10/2016 5:54 AM, Seth wrote:
> On 23-10-16 21:40, Exagon wrote:
>> I tried to minimize the code arround the expression parser, but its somehow
>> not that trivial.
>
> I've noticed similar issues with much simpler code:
> https://stackoverflow.com/questions/37230653/compile-times-with-boost-spirit-x3/37242969#37242969
>
> Quoting my own comments there
>
>> @RichardHodges This timing though is certainly indicative of a bug/implementation flaw.
> Usual X3 grammars this would compile in seconds. I'd expect 10s maybe due to the other
> uses of variants (|apply_visitor|) which are quite template heavy. But as you can see in
> my answer, the situation is a lot more severe than this. – sehe
> <https://stackoverflow.com/users/85371/sehe> May 15 at 19:52
> <https://stackoverflow.com/questions/37230653/compile-times-with-boost-spirit-x3/37242969#comment62014796_37230653>
>
>
> <https://stackoverflow.com/questions/37230653/compile-times-with-boost-spirit-x3/37242969#comment62014796_37230653>
>
> Do any of our X3 buffs know what is going on?
>
> I personally think it's instantiation depth in the face of aggressively inlining
> compilers. (It's hard to decide what is the best approach. We want inlining, but at what
> cost? Is there a good, library-defined, cut-off point?)

Sorry I'm very late! Let me tackle this, one step at a time...

I tried the stackoverflow code. It's compiling here (2015 Macbook pro i7 16GB) in under
a few seconds. It didn't even hit memory that hard. What are you guys getting and
what compiler/platform?

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