Mail Archives: djgpp/1996/01/06/01:08:31
> [It's slow]
> I get the "virtual memory exhausted" message from cc1plus, even
> though my temp dir's got 38 megs free, and the drive the source is on
> I'm using CWSDMPI beta6, if that matters - someone on the list
*DON'T* use anything but CWSDPMI beta9 with V2 beta 4. The sbrk()
algorithm was changed to use multiple memory zones. CWSDPMI beta 7
and before put each zone into a separate area of memory, and limited
them to 15 max. The 15 max causes the VM exhausted messages; the different
zones exhausts the page directory entries which then page like crazy
(so it seems like the program is running in 1/2Mb of memory). So the
problems you are seeing are a CWSDPMI bug/limitation. Upgrade to beta9,
the zip file is only 37Kb for crying out loud!
Oh, and unless you CWSPARAM edit your CWSDPMI image, it will always
page onto C:\CWSDPMI.SWP (It doesn't look at TEMP).
a 4, set LFN=N was introduced so you could
make projects expecting truncation (like GCC). But due to an incomplete
opendir implementation (still discussing details) all file names are lowercased
even when LFNs are enabled. This isn't a problem on VFAT drives, but it
CAN be on network drives if case sensitive. If someone wants to work with
me on the details of the LFN libc stuff under SAMBA, I would be willing
to help find and fix the bugs.
- Raw text -