#2307 closed Bugs (fixed)
Runaway compiler memory use in test
Reported by: | Dave Abrahams | Owned by: | John Maddock |
---|---|---|---|
Milestone: | Boost 1.37.0 | Component: | math |
Version: | Boost 1.35.0 | Severity: | Problem |
Keywords: | Cc: |
Description (last modified by )
On GCC-4.1.0 just compiling the test_ibeta_real_concept and test_binomial_real_concept tests consume over 1.6G of memory before I decide that the swapping is unacceptable and I kill cc1plus. That leads me to suspect strongly that source:/trunk/status/explicit-failures-markup.xml@48168#L3411 wrongly blames the running time of the test. It seems to me that these tests might be made to work by breaking up the source files into chunks that are manageable by the compiler.
I'm happy to give you access to a system where you can experience the issue firsthand if you don't have one yourself.
Change History (7)
comment:1 by , 14 years ago
Description: | modified (diff) |
---|
comment:2 by , 14 years ago
Description: | modified (diff) |
---|
comment:3 by , 14 years ago
Status: | new → assigned |
---|
comment:4 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
OK, I've managed to get memory usage down to 200Mb with Mingw GCC-4.3, can't at present see how to reduce it further without sacrificing test coverage.
Closing for now, please reopen if this doesn't work for you.
comment:5 by , 14 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Hum; I guess I'm reopening this one.
- The same problem occurs with test_ibeta_inv_real_concept and test_ibeta_real_concept
- I still think explicit-failures-markup.xml probably needs to be fixed.
comment:6 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
I'll try and fix this, but it's not that easy: I tried splitting the real_concept tests into 7 parts, but the memory consumed stayed the same (about 400Mb on Mingw), this compares to just 50Mb for msvc :-(
I'll have to look into this some more.
John.