Xref: news2.mv.net comp.os.msdos.djgpp:1191 From: wald AT theory DOT lcs DOT mit DOT edu (David Wald) Newsgroups: comp.os.msdos.djgpp Subject: Re: DJGPP v2 woes :( Date: 14 Feb 1996 20:38:51 GMT Organization: Theory of Computation, LCS, MIT Lines: 30 Message-ID: References: <4fpm6c$an AT news DOT uni-c DOT dk> <4fqaj7$2qu AT fu-berlin DOT de> <31215a13 DOT sandmann AT clio DOT rice DOT edu> NNTP-Posting-Host: woodpecker.lcs.mit.edu In-reply-to: Charles Sandmann's message of Tue, 13 Feb 1996 21:42:11 CST To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp In article <31215a13 DOT sandmann AT clio DOT rice DOT edu> Charles Sandmann writes: >> must also say, that my C++ code is using lots of inlined templating >> (it's only one object file from over 10000 lines of code) for speed > >Sounds like a candidate for the CWSDPMI bug, sigh. > >ftp.neosoft.com:pub/users/s/sandmann/csdpmi1heapfix.zip > >I guess beta testers don't compile huge C++ codes under DOS :-P Sorry, but we're all coming out of the woodwork now. I'm hitting the same sort of problem (infernal compiler error with when compiling template-laden C++ code). Unfortunately, heapfix isn't a full solution for me: it allows me to compile a few more files, but I've got a couple of files which won't compile no matter how high I bump the heap. (At least, until heapfix bumps the heap beyond x9400, at which point I no longer have a runnable CWSDPMI.EXE.) All of these files do compile with GCC 2.7.2 on other platforms, so I suspect I'm not just running afoul of a general GCC bug. Also, I'm running this on a pretty resource-rich system (64MB RAM, ~500MB free disk space), so hope the problem isn't at the hardware end. DOS, DPMI and DJGPP are a mystery to me, though, so I'm happy for any other suggestions you can provide. -David -- ============================================================================ David Wald http://theory.lcs.mit.edu/~wald/ wald AT theory DOT lcs DOT mit DOT edu ============================================================================