Re: Horrible compiletimes and memory usage while compiling a parser with X3
Exagon <[email protected]>
| Newsgroups | gmane.comp.parsers.spirit.general |
|---|---|
| Message-ID | <[email protected]> |
I dont believe I can break this down to one cpp. 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. 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. Greetings Exagon -- View this message in context: http://boost.2283326.n4.nabble.com/Horrible-compiletimes-and-memory-usage-while-compiling-a-parser-with-X3-tp4689104p4689544.html Sent from the spirit-general mailing list archive at Nabble.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