January 21, 2012 [Issue 1382] memory allocated for arrays in CTFE functions during compilation is not released | ||||
---|---|---|---|---|
| ||||
Posted in reply to d-bugmail | http://d.puremagic.com/issues/show_bug.cgi?id=1382 Don <clugdbug@yahoo.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|2.059 |--- --- Comment #9 from Don <clugdbug@yahoo.com.au> 2012-01-21 01:26:54 PST --- Please don't set milestones without consultation (unless you plan to fix the bug yourself). This bug is still open because it is HARD. I've been slowly making progress on it for the last year. It's not going to be fixed soon -- the remaining work to be done is still about the equivalent of 30 avarage bugs. However, 90% of the symptoms were fixed in 2.049. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- |
January 23, 2012 [Issue 1382] memory allocated for arrays in CTFE functions during compilation is not released | ||||
---|---|---|---|---|
| ||||
Posted in reply to d-bugmail | http://d.puremagic.com/issues/show_bug.cgi?id=1382 Leandro Lucarella <leandro.lucarella@sociomantic.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |leandro.lucarella@sociomant | |ic.com --- Comment #10 from Leandro Lucarella <leandro.lucarella@sociomantic.com> 2012-01-23 02:41:48 PST --- Is there any technical reason not to use the Bohem GC as a temporary workaround until this can get properly fixed? I'm just curious. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- |
January 23, 2012 [Issue 1382] memory allocated for arrays in CTFE functions during compilation is not released | ||||
---|---|---|---|---|
| ||||
Posted in reply to d-bugmail | http://d.puremagic.com/issues/show_bug.cgi?id=1382 --- Comment #11 from Walter Bright <bugzilla@digitalmars.com> 2012-01-23 11:23:06 PST --- I made an experimental build of dmd that uses a gc. The compiler slowed down quite a bit. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- |
January 24, 2012 [Issue 1382] memory allocated for arrays in CTFE functions during compilation is not released | ||||
---|---|---|---|---|
| ||||
Posted in reply to d-bugmail | http://d.puremagic.com/issues/show_bug.cgi?id=1382 --- Comment #12 from Leandro Lucarella <leandro.lucarella@sociomantic.com> 2012-01-24 02:19:04 PST --- (In reply to comment #11) > I made an experimental build of dmd that uses a gc. The compiler slowed down quite a bit. In which cases did you tried it? For files that allocates a lot of "CTFE memory" it should be the other way around, as the memory consumption is so high that the system is using most of the time moving things around between the memory and the swap. Do you have a patch that I can try (for D1)? Thanks. As bad as it sounds, maybe a good tradeoff would be to add a command line option (as obscure an undocumented as you want) to activate the GC for cases where not using it is not really an option. Being that it seems that this bug is really hard, I think it might deserve looking for a workaround to be able to use the compiler in this extreme cases in the short term. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- |
January 24, 2012 [Issue 1382] memory allocated for arrays in CTFE functions during compilation is not released | ||||
---|---|---|---|---|
| ||||
Posted in reply to d-bugmail | http://d.puremagic.com/issues/show_bug.cgi?id=1382 --- Comment #13 from Walter Bright <bugzilla@digitalmars.com> 2012-01-24 02:29:36 PST --- I tried it by building the library and running its unittests, and running the test suite. It was considerably slower. The GC used was the old C++ version of the D runtime GC. You can build it by switching the GCOBJS macro in win32.mak. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- |
January 24, 2012 [Issue 1382] memory allocated for arrays in CTFE functions during compilation is not released | ||||
---|---|---|---|---|
| ||||
Posted in reply to d-bugmail | http://d.puremagic.com/issues/show_bug.cgi?id=1382 --- Comment #14 from Leandro Lucarella <leandro.lucarella@sociomantic.com> 2012-01-24 02:37:46 PST --- (In reply to comment #13) > I tried it by building the library and running its unittests, and running the test suite. It was considerably slower. > > The GC used was the old C++ version of the D runtime GC. > > You can build it by switching the GCOBJS macro in win32.mak. Oh, I was talking about the Bohem GC, the one tried by Christian Kamm, which is a pretty good state of the art collector AFAIK. I think LDC used it (I don't know if it still does) with pretty good results (see comment 3). Maybe Christian can give us some more information about it :) -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- |
January 24, 2012 [Issue 1382] memory allocated for arrays in CTFE functions during compilation is not released | ||||
---|---|---|---|---|
| ||||
Posted in reply to d-bugmail | http://d.puremagic.com/issues/show_bug.cgi?id=1382 --- Comment #15 from Don <clugdbug@yahoo.com.au> 2012-01-24 06:21:47 PST --- An important thing to realize about this bug is that it is *not* the primary cause of slow performance and high memory consumption in CTFE. Fixing this bug would make very little difference, except in cases involving concatenation. I think it's had a lot of votes because people think it's the key CTFE performance issue, but actually the bad guy is bug 6498. Which is easier to fix. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- |
Copyright © 1999-2021 by the D Language Foundation