Re: Horrible compiletimes and memory usage while compiling a parser with X3
Joel de Guzman <[email protected]>
| Newsgroups | gmane.comp.parsers.spirit.general |
|---|---|
| Message-ID | <[email protected]> |
On 03/11/2016 9:15 AM, teajay wrote: > Le 26/10/2016 à 19:03, Exagon a écrit : >> of course these are the numbers of my project, which has some more code under >> the hood, I I dont think the example of the problem will generate a binary >> as big as the one from my project was, but the source of the bad compile >> times and huge binarys can definetly be found in the small example I showed >> you. >> Greetings Exagon >> > > I managed to get the code compiled successfully with a reasonable > compile time and memory usage with the latest clang version. I didn't > have any success with gcc however. > > I tried to identify template instantiations loops using templight but > found nothing really bothering. > > I guess you ran into a case where spirit drove the compiler over the > edge, or into a bug. This can happen. Sometimes a new compiler helps get > the problem fixed. For those willing to help do some investigation, the issue is what really is the compiler instantiating and why there's a lot. I'm guessing there might be an excessive instantiation loop from top-level to the leaves and up again. The error trace provides the instantiation information. 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